> For the complete documentation index, see [llms.txt](https://docs.evedex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.evedex.com/key-features-and-components/trading-platform-and-matching-engine/arbitrum-l3-and-on-chain-settlement.md). # Arbitrum L2 and on-chain settlement On-chain settlement refers to the process of finalizing transactions directly on Arbitrum. Unlike centralized exchanges, where trades are executed and settled off-chain within the exchange's internal ledger, EVEDEX leverages blockchain technology to ensure transparency, security, and self-custody. #### Interaction Between EVEDEX Core Engine and Blockchain User actions are periodically recorded in the blockchain to verify and ensure the correctness of the backend data. Key scenarios include: * **Periodic Updates**: User position data is written to the blockchain after sufficient changes have accumulated. * **Withdrawals**: When a user withdraws funds, the data is recorded on-chain to verify backend correctness. --- # 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.evedex.com/key-features-and-components/trading-platform-and-matching-engine/arbitrum-l3-and-on-chain-settlement.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.