> 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/bsc/gateway.md). # Running a Gateway The **bloXroute Gateway** is open-source software that connects to the **Blockchain Distribution Network (BDN)**, giving users high-performance access to blockchain data and transaction propagation. A Gateway enables two key capabilities: * **Fast transaction submission** into the BDN * **Real-time streaming** of blocks and transactions from the BDN Gateways are typically deployed alongside a full blockchain node, using the node’s native peer-to-peer protocol (e.g., Ethereum’s devp2p). However, **Enterprise-tier clients** may run a Gateway **without operating their own node**, instead connecting through a remote proxy maintained by bloXroute. Note that Gateways do **not** validate chain state or store blockchain data. They serve purely as a communication layer between your infrastructure and the BDN. #### **What You'll Find in This Section** This section explains how to run a bloXroute Gateway, including: * **Supported Clients** – Which blockchain nodes and networks are compatible * **Requirements** – Hardware, bandwidth, and latency expectations * **Authentication** – API keys and certificates required for BDN access * **Installation** – Deploying via GitHub or Docker * **Configuration & Startup** – Connecting your Gateway to the BDN and (optionally) your full node * **Operation & Maintenance** – Monitoring, logs, upgrades, and best practices --- # 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/bsc/gateway.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.