> 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/robinhood/submit-transactions/speed-boost.md). # Speed Boost The **Speed Boost** Service provides a fast and reliable way to submit transactions on Robinhood Chain. Transactions are routed through bloXroute's optimized infrastructure to the sequencer, enabling faster and more consistent propagation. Robinhood Chain orders transactions strictly by arrival time at the sequencer, which makes delivery speed the primary factor in landing your transaction ahead of competing flow. Key characteristics: * **Multi-path submission** – Each transaction is sent over multiple network paths to the sequencer simultaneously, and the fastest one wins — so your transaction consistently arrives by the fastest available route rather than a single, randomly-assigned one. * **Fast and consistent** – By racing multiple paths, Speed Boost reduces the latency and variability of reaching the sequencer. * **BDN reliability** – Transactions are delivered through bloXroute's Blockchain Distribution Network (BDN), providing redundancy and optimal routing. The submission method is the same as regular transaction submission - the performance improvement comes from the optimized routing used by the service. #### Submission Endpoint For submission details please refer to [Submit Transactions](https://docs.bloxroute.com/robinhood/submit-transactions/private-transactions). --- # 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/robinhood/submit-transactions/speed-boost.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.