> For the complete documentation index, see [llms.txt](https://docs.axiomprotocol.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.axiomprotocol.io/whitepaper/bootstrap-phase/how-bootstrap-mode-ends.md).

# How Bootstrap Mode Ends

Bootstrap mode ends in one of two ways, whichever happens first.

#### **1. Voluntary Deactivation by Bootstrap Signers**

Any 3 bootstrap signers can collectively vote to deactivate bootstrap mode. This occurs when:

* There is sufficient organic trading volume
* The top 50 percent set has stabilized
* Staker participation is high
* Markets are being created and resolved by users
* Governance participation is healthy

Because signers are globally distributed and independent, this requires a multi-party decision, not unilateral control.

#### **2. Automatic Expiry**

Bootstrap mode automatically terminates **12 months after deployment**. This is enforced by the protocol and cannot be extended.

Once bootstrap ends:

* Market creation is fully permissionless for top 50 percent stakers
* Outcome governance transitions to fully decentralized mode
* Bootstrap signers lose all special privileges

Axiom becomes a fully decentralized system.


---

# 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.axiomprotocol.io/whitepaper/bootstrap-phase/how-bootstrap-mode-ends.md?ask=<question>&goal=<user_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.