> 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/implementation-design.md).

# Implementation Design

| Contract                          | Function                                           |
| --------------------------------- | -------------------------------------------------- |
| `XRPVault` (future stable vaults) | Staking, share accounting, reward distribution     |
| `EligibilityRegistry`             | Snapshot and percentile tracking                   |
| `FeeRouter`                       | Routing staker fees and yield flows                |
| `MarketFactory` (upgradeable)     | Market creation and implementation deployment      |
| `AxiomConditionalTokens`          | ERC-1155 positions, split, merge, redeem           |
| `AxiomCTFMarket`                  | Per-market condition wrapper and resolution oracle |
| `AxiomCTFExchange`                | Onchain CLOB settlement for matched trades         |
| `AxiomRewards`                    | Onchain claims for epoch-based rewards             |

Upgradeable Market Factory: UUPS proxy pattern to evolve implementation registration and deployment logic over time. Upgrade control transitions from launch administration to more decentralized governance over time.

Upgrade admin staged transition:

1. Dev EOA (Phase 1)
2. 3-of-5 multisig (Phase 2)
3. Governance-controlled timelock and multisig (Phase 3)


---

# 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/implementation-design.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.