> For the complete documentation index, see [llms.txt](https://rocketfoundation.gitbook.io/rocket-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rocketfoundation.gitbook.io/rocket-docs/rocket/quickstart.md). # Overview ### RocketChain RocketChain is a high performance blockchain for derivatives trading. It features a powerful HFT resistant matching engine and consensus mechanism for fair benefit and access to all users. ### Consensus #### Rocket Consensus RocketFi is powered by RocketBFT, a custom-built consensus algorithm designed for high-performance trading. I makes adjustments on consensus mechanisms like HyperBFT and MonadBFT, optimizing for low-latency and high-throughput of trading instructions. ### Execution RocketChain runs an auction matching engine which batches orders in sub-second blocks and finds fair value which maximizes fills. All orders execute at their price or better (negative slippage) and market orders can fill each other to further reduce slippage. As there is no preferential ordering or price, low latency traders cannot front-run or extract significant value from their peers. This all takes place on the order of milliseconds so there is no disruption to a regular human user. *** > 🔧 Execution improvements are planned as demand scales. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://rocketfoundation.gitbook.io/rocket-docs/rocket/quickstart.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.