> For the complete documentation index, see [llms.txt](https://docs.xyo.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyo.network/developers/cookbook/prepare-for-mainnet.md). # Prepare for Mainnet Review an XL1 application before moving from Sequence to Mainnet. **Owner:** XYO Layer One maintainers ยท **Last verified:** September 17, 2026 Mainnet uses real XL1 and irreversible public transactions. Complete this review before changing the configured network. ## Application * All payload schemas and size bounds are explicit. * Application payloads are validated after every read. * The selected network and account are visible before approval. * Duplicate submission and uncertain-result behavior are documented. * Finality is observed through `@xyo-network/xl1-sdk`, not inferred from submission. ## Security * Browser code never receives recovery phrases, private keys, or provider secrets. * Server-side secrets use an approved secret store and rotation process. * Logs and errors are reviewed for credential leakage. * Dependencies are limited to reviewed public npm libraries. ## Operations * Sequence tests cover reconnects, insufficient balance, rejected transactions, and delayed finality. * Indexers resume from durable finalized checkpoints. * Alerts distinguish provider availability, submission, inclusion, and finality. * Rollback and incident owners are named before launch. --- # 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.xyo.network/developers/cookbook/prepare-for-mainnet.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.