Comment on page
Reducing Latencies using the BDN
If you are a DeFi trader, you care about transaction latency. You need to quickly hear about transactions and want your transactions to arrive at Validators as soon as possible. The information below will help you understand your expected latencies from using the BDN.
There are three factors that determine how fast a validator 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 the 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 an Introductory user.
3. Private Relays Enterprise Elite users and above 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.
Enterprise, Enterprise Elite and Ultra plans can expect up to 30 milliseconds (ms) faster propagation compared to Professional, and Introductory plans everywhere.
Shared Private Link is automatically enabled for traders with an Enterprise plan or above: an improvement of up to 50ms in propagation to and from China is expected. Transactions sent by a node via the Ethereum protocol to a Gateway (transactions propagated from node to gateway via p2p) are expected to be 25-50 ms slower than transactions sent to the gateways using the blxr_tx endpoint.