> For the complete documentation index, see [llms.txt](https://docs.axis.to/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.axis.to/readme.md).

# Axis Protocol Docs

Axis Protocol is a synthetic dollar protocol that mints a yield-bearing synthetic dollar backed by whitelisted collateral assets. The protocol generates yield through cross-asset arbitrage, then distributes it to stakers through a tokenized vault.

***

## Core Contracts

| Contract                    | Purpose                                           |
| --------------------------- | ------------------------------------------------- |
| `AxisUSD`                   | ERC-20 synthetic dollar with whitelisted minting  |
| `AxisUSDMinting`            | Mint/redeem engine with EIP-712 signed orders     |
| `StakedAxisUSDV2`           | ERC-4626 staking vault with configurable cooldown |
| `AxisUSDSilo`               | Escrow for funds during cooldown periods          |
| `StakingRewardsDistributor` | Automated reward distribution                     |
| `AxisUSDRateProvider`       | Exchange rate oracle for external integrations    |

***

## How It Works

**Minting:** Users sign EIP-712 orders off-chain. Operators submit them on-chain, pull collateral, and mint USDx.

**Staking:** Users deposit USDx into the vault and receive sUSDx shares. Share value increases as rewards vest over 8-hour periods.

**Redemption:** Users sign redeem orders. Operators submit them on-chain, burn the USDx, and return collateral.

***

## Audience Guide

| Audience                          | Start Here                                        | Looking For                                               |
| --------------------------------- | ------------------------------------------------- | --------------------------------------------------------- |
| **End User / Investor**           | [Quickstart](/getting-started/quickstart.md)      | How to mint, stake, and earn yield                        |
| **Integrator / Developer**        | [Mint & Redeem](/guides/mint-and-redeem.md)       | EIP-712 signing flow, SDK commands, contract interfaces   |
| **Auditor / Security Researcher** | [Security & Audits](/concepts/security.md)        | Invariants, admin powers, edge cases                      |
| **Regulator / Institution**       | [Compliance](/legal-and-compliance/compliance.md) | Risk disclosures, admin transparency, jurisdictional info |
| **Token Holder / Governance**     | [Governance](/concepts/governance.md)             | Decision-making process, admin key management             |

***

## Documentation Structure

This documentation follows the [Diataxis framework](https://diataxis.fr/) with strict quadrant separation:

| Section                                                   | Quadrant    | Audience                 | Purpose                                          |
| --------------------------------------------------------- | ----------- | ------------------------ | ------------------------------------------------ |
| [Getting Started](/getting-started/quickstart.md)         | Tutorial    | New users                | First successful interaction with the protocol   |
| [Concepts](/concepts/architecture.md)                     | Explanation | All readers              | Understand *why* the system is designed this way |
| [Guides](/guides/mint-and-redeem.md)                      | How-to      | Integrators, operators   | Step-by-step instructions for specific tasks     |
| [Reference](/reference/core-contracts.md)                 | Reference   | Developers, auditors     | Complete technical specifications                |
| [Legal & Compliance](/legal-and-compliance/compliance.md) | Explanation | Institutions, regulators | Risk disclosures and jurisdictional info         |

{% hint style="info" %}
**Tutorials** teach by doing. **Concepts** explain the reasoning behind design choices. **Guides** give step-by-step instructions for specific tasks. **Reference** catalogs every function, event, and error. Each section links to the others but stays within its quadrant.
{% endhint %}

***

## Quick Links

* **I'm new** -- start with [Quickstart](/getting-started/quickstart.md)
* **I want to understand the system** -- start with [Architecture](/concepts/architecture.md)
* **I want to integrate** -- start with [Mint & Redeem](/guides/mint-and-redeem.md) or [Stake & Unstake](/guides/stake-and-unstake.md)
* **I want to look up a function** -- go to [Core Contracts](/reference/core-contracts.md) or [Staking Contracts](/reference/staking-contracts.md)
* **I want contract addresses** -- go to [Contract Addresses](/reference/contract-addresses.md)
* **I want to understand the risks** -- read [Security & Audits](/concepts/security.md) and [Compliance](/legal-and-compliance/compliance.md)

***

## Build & Origin

| Property         | Value                                                                                 |
| ---------------- | ------------------------------------------------------------------------------------- |
| Solidity version | `0.8.30`                                                                              |
| OpenZeppelin     | v5.4                                                                                  |
| Framework        | Foundry                                                                               |
| Origin           | Fork of [Ethena](https://github.com/ethena-labs/bbp-public-assets) (commit `f3e56d5`) |


---

# 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:

```
GET https://docs.axis.to/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.