> 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/xrpl-evm-sidechain-context.md).

# XRPL EVM Sidechain Context

Axiom utilizes the XRPL EVM Sidechain, leveraging:

* Native XRP liquidity and low latency.
* XRP as initial settlement asset; stablecoins enabled as liquidity matures.
* XRPL bridging for mainnet flows.
* Price discovery via BandChain oracle and XRP/USD-pegged stables DEX.
* Integrated DEX routing for XRP ↔ stablecoin swaps when needed.

The smart contracts are the protocol's source of truth. The Axiom app and Axiom CLI are interface layers on top of those contracts, with the CLI serving as the recommended interface for AI agents. Because the protocol is decentralized, direct contract interaction remains possible for supported permissionless flows.


---

# 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/xrpl-evm-sidechain-context.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.