> For the complete documentation index, see [llms.txt](https://docs.roguechain.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roguechain.io/rogue-protocol/rogue-chain/instant-transaction-finality.md). # Instant Transaction Finality Rogue Chain's use of a Sequencer that processes transactions instantly in the order they are received has many benefits, including reducing gas costs and preventing front-running of game result transactions by corrupt miners. But using a Sequencer instead of a mempool also removes the possibility of chain reorgs, meaning that transactions on Rogue Chain have instant time-to-finality. Most other EVM chains require you to wait a certain number of blocks before considering a transaction to be final, making it impossible to run fast-paced betting games or to pay out winning bets instantly. On Rogue Chain we can confirm all bets instantly and move on with the game. And your winning bets will never be cancelled later in a chain reorg, meaning we can pay out winning bets instantly. --- # 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://docs.roguechain.io/rogue-protocol/rogue-chain/instant-transaction-finality.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.