> 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/protocol-design/bootstrap-launch-mechanism/multi-signer-bootstrap-authority.md).

# Multi-Signer Bootstrap Authority

Design:

* Authorization Registry holds 5-10 signer addresses.
* Each signer can independently create markets and submit proposals (bypassing top 50% checks).
* Geographic distribution and action transparency via events.

Authorized operations include market creation, proposal submission, adding vaults, whitelisting settlement tokens, and rate-limiting.

Rate limits per signer:

* 5 markets/day
* 10 proposals/day

All bootstrap actions emit events such as:

```solidity
event BootstrapMarketCreated(address indexed signer, uint256 indexed marketId, string title);
event BootstrapProposalSubmitted(address indexed signer, uint256 indexed marketId, uint8 outcome);
```


---

# 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.axiomprotocol.io/protocol-design/bootstrap-launch-mechanism/multi-signer-bootstrap-authority.md?ask=<question>&goal=<endgoal>
```

`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.