> For the complete documentation index, see [llms.txt](https://soldexai.gitbook.io/soldex-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://soldexai.gitbook.io/soldex-whitepaper/features.md).

# Features

**Permissionless**&#x20;

Trade perpetual on any pairing. Our governance will ensure that the best trading pairs are available and that only the safest oracles are used.

**Efficiently Incentivized Liquidity**

Liquidity pool trading is predicated on having enough assets in each pool in order to facilitate instant trades. Soldex addresses this requirement by incentivizing users to deposit assets and provide liquidity.

**Community Governance**

Token holders can establish consensus by voting on the governance proposals or introducing new proposals for a vote.

**Ecosystem Foundation Layer**

Attract assets and build incentives that can empower an ecosystem of financial products.

**Real-time Settlement and Light-speed swaps**

Fast trading experience with automatic deposit directly to your wallet.&#x20;


---

# 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://soldexai.gitbook.io/soldex-whitepaper/features.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.
