⏩ BDN Latencies

If you are a DeFi trader, you care about transaction latency. You need to quickly hear about transactions and want your transactions to arrive to miners and mining pools as soon as possible. The information below will help you understand your expected latencies from using the BDN.

Speed of Sending Transactions

There are three factors that determine how fast a mining pool will hear about your transactions.

1. Your bot location (or any application that generates transactions) It is important that your bot is close to the Relay network and has low latency. Users that are using the Gateway-API (even if the Gateway is locally installed with no latency) should measure the latency to the Relay network. Users using the Cloud-API, should measure the latency to the Cloud-API.

2. Priority Handling The BDN processes all transactions extremely fast, but gives priority to users based on their tier of plan. For example, if two users submit a transaction to the same BDN Relay at the same time, the Relay will process the transaction from the Enterprise user before the Developer user.

3. Shared Private Link to China The BDN offers users with Enterprise plans access to a dedicated shared private link to China. The Private Link improves the issue of performance consistency over public links and reduces the latency of sending and receiving data from China. This is critical for DeFi traders, as many mining pools have nodes located in China.

Latencies Variances by Tiers

You can expect up to a 5 millisecond (ms) difference in propagation outside of China between Enterprise/Professional plans and Developer/Introductory plans. You can expect up to a 50 ms improvement from the Shared Private Link to and from China. Transactions that are received from the node to the Gateway via the Ethereum protocol (not using blxr_tx endpoint) are expected to be 25-50 ms slower.