> 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/future-extensions.md).

# Future Extensions

### Multi-Asset Staking

Support for LSDs, wrapped assets, and synthetic positions is possible but requires robust oracles and risk controls.

### Cross-Market Arbitrage

Atomic swaps and liquidity aggregation across correlated markets to improve price discovery and attract market makers.

### Automated Templates

Standard market templates (sports, crypto price targets, macro, on-chain events) to reduce friction and standardize evidence sources.

### AI-Based Proposal Scoring

Optional off-chain advisory models to analyze evidence, surface sentiment, and flag low-credibility sources. Advisory only—final decisions remain with stakers.

### SubDAO Layer

Specialized working groups (SubDAOs) for domain-specific proposals and delegated voting, receiving budgets and vetting proposals before full governance submission.


---

# 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/future-extensions.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.