> 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/architecture/overview.md).

# Architecture overview

Exliquid is organized around one idea: **trading actions update a shared market state through native network execution, and applications consume the resulting market and account data through stable client interfaces**.

![Exliquid logical architecture](https://1310468402-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuAWTUuLpxZ37CPZEwFWV%2Fuploads%2Fgit-blob-bce87e8def42191a7e312e80137f4f85863af2c1%2Flogical-architecture.svg?alt=media)

## Public logical layers

### Clients and integrations

Users and automated systems interact through:

* the User App;
* TypeScript or Python SDKs;
* trading bots and market-making systems;
* REST and WebSocket clients.

These clients submit signed actions and consume market/account data. They do not need access to validator internals or storage implementation.

### API and streaming layer

The public interfaces provide:

* market and account queries;
* signed transaction submission;
* transaction confirmation;
* real-time market streams;
* authenticated account streams;
* testnet session and faucet flows where enabled.

See [Developer overview](/docs/developers/overview.md).

### Exliquid network

The network orders valid actions, executes the native trading rules and finalizes the resulting shared market state.

From an external integration perspective, the important property is not which internal component performs each step, but that an accepted transaction has a well-defined lifecycle from submission to committed result.

### Native trading engine

The trading engine updates the connected trading domains together:

* order book and matching;
* accounts and balances;
* positions and PnL;
* market prices and funding;
* margin and risk;
* liquidation and loss handling.

These areas are intentionally integrated so a fill, balance change, position change and risk result cannot become separate competing truths.

### Shared market state and data access

Committed trading outcomes are exposed as user-facing market, account and transaction views. REST is used for point-in-time queries and confirmation; WebSocket is used for low-latency updates.

Clients should treat transaction submission acknowledgement and committed confirmation as distinct stages. See [Trading lifecycle](/docs/architecture/trading-lifecycle.md).

## What this diagram intentionally does not show

This public architecture does not document internal package structure, storage engines, database topology, consensus adapters, service process layout, deployment scripts or recovery internals. Those are implementation concerns and are not required to integrate with Exliquid.


---

# 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/architecture/overview.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.