> For the complete documentation index, see [llms.txt](https://docs.bloxroute.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloxroute.com/core-solutions/blockchain-distribution-network-bdn/network-components.md). # Architecture The bloXroute BDN is built on a globally distributed infrastructure designed to deliver low-latency propagation of blockchain data. This section introduces the core components of the network and explains how they work together to accelerate transaction and block delivery across supported chains. #### Gateway Each participant in the BDN runs a Gateway alongside their blockchain full node. The Gateway serves as the connection point between your node and bloXroute’s network. * Communicates using the native protocol of your blockchain (e.g., Ethereum). * Forwards blocks and transactions to and from the BDN. * Does not validate the blockchain or store its state. #### Control Plane The Control Plane ensures the network remains performant and resilient by coordinating connections between Gateways and Relays. * Determines optimal Relay connections based on the Gateway's IP geolocation. * Continuously manages network topology. * Provides peer discovery to maintain Gateway connectivity even if the Control Plane is unavailable. #### Relays Relays are high-performance servers that act as distribution hubs within the BDN. They’re globally distributed and optimized for minimal propagation delay. * **Transaction Relays**: Propagate transactions across the network. * **Block Relays**: Propagate compressed blocks. * The split-relay architecture keeps transaction and block traffic separate and efficient. #### Remote Blockchain Nodes Gateways occasionally need access to blockchain data they cannot validate. In these cases, bloXroute provides remote full nodes to fulfill such requests. * Used for fallback queries from your full node. * Ensures uninterrupted service when local data isn’t sufficient. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.bloxroute.com/core-solutions/blockchain-distribution-network-bdn/network-components.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.