⏩ 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 and has low latency to the Relay network. Users that are using the Gateway-API (even if the Gateway is locally installed with no latency) should measure their latency to the Relay network. Users using the Cloud-API, should measure their 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 an Enterprise user before a 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.

4. Private Relays Enterprise users can now utilize Private Relays, which can significantly improve latency in regions that have high latencies to the BDN's Public Relays. See Private Relays - Get Closer to the BDN for more information.

Latency Variances by Tiers

Enterprise and Enterprise Elite plans can expect up to 10 milliseconds (ms) faster propagation compared to Professional, Developer and Introductory plans everywhere except China.

Enterprise and Enterprise Elite plans with a Shared Private Link can expect up to 50ms improvement in propagation to and from China. Transactions received by a node via the Ethereum protocol (and not using the blxr_tx endpoint) and sent to a Gateway are expected to be 25-50 ms slower.