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

# Exliquid Documentation

Exliquid is a trading-focused application chain built around native order-book execution, integrated account and risk state, and externally verifiable transaction results.

This GitBook is the public product and integration documentation for Exliquid. It is written for:

* traders and market makers who need to understand trading behavior;
* developers integrating through the SDKs, REST API or WebSocket feeds;
* technical evaluators who need a product-level view of the network and trading model.

It is **not** a guide to developing the Exliquid node software or reproducing its internal implementation.

{% hint style="warning" %}
Exliquid is currently an experimental simulated-asset network line. Real-asset deposits, withdrawals, custody and bridging are not supported, and public testnet endpoints are listed only after they are explicitly opened.
{% endhint %}

## Start here

* [What is Exliquid?](/docs/start-here/overview.md)
* [Network status and limitations](/docs/start-here/current-status.md)
* [Trading overview](/docs/trading/overview.md)
* [Architecture overview](/docs/architecture/overview.md)
* [Developer overview](/docs/developers/overview.md)
* [Security and limitations](/docs/security/security.md)

## Documentation map

### Trading

Learn the behavior that directly affects users and integrations: order matching, balances, positions, price references, funding, margin and liquidation.

### Architecture

Understand the public logical architecture: how signed actions enter the network, how the native trading engine updates shared market state, and how applications consume the resulting data.

### Developers

Build trading terminals, bots, market-making systems, analytics tools and account integrations using the supported SDK, REST and WebSocket contracts.

### Security and reference

Check the current network boundary, signing/network identifiers, compatibility policy, known limitations and disclosure guidance.

## Public documentation boundary

Public documentation explains **what external users and integrations can rely on**. It intentionally avoids internal package structure, storage layout, process topology, implementation-specific consensus adapters, mempool internals, database schemas, deployment scripts and engineering experiments.

When a detail is relevant only to Exliquid core development, it belongs with the source repository and internal engineering material rather than in this GitBook.

## Official destinations

* Website: <https://exliquid.org>
* Documentation: <https://exliquid.gitbook.io/docs>

Public App, API, WebSocket, Explorer and Faucet URLs are published in [Networks and versions](/docs/reference/networks-and-versions.md) only after they are available for use.


---

# 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://exliquid.gitbook.io/docs/readme.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.