> 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/reference/networks-and-versions.md).

# Networks and versions

This page is the source of truth for **public Exliquid network availability and client compatibility**.

A route or chain identifier appearing in source code does not mean a public service is open.

## Current network

| Network                  | Status                       | Chain ID                    | REST API      | WebSocket     | User App / Explorer | Faucet        |
| ------------------------ | ---------------------------- | --------------------------- | ------------- | ------------- | ------------------- | ------------- |
| Public-testnet candidate | **Access not yet published** | `exliquid-public-testnet-5` | Not published | Not published | Not published       | Not published |

Documentation is available at:

`https://exliquid.gitbook.io/docs`

Website:

`https://exliquid.org`

## Client compatibility

For each public network, this page will publish the external compatibility tuple required by integrations:

* network / chain identity;
* REST API version and base URL;
* WebSocket version and URL;
* supported TypeScript SDK version;
* supported Python SDK version;
* signing-domain identifiers;
* reset/migration notices;
* known client-visible limitations.

## Current route versions

The current client contracts use:

```
REST:      /api/v1
WebSocket: /ws/v1
```

A route version describes the external API contract. It does not imply that a public base URL has already been opened.

## Public endpoint rule

Only use an endpoint when it is listed on this page as public.

Do not treat the following as supported public contracts unless explicitly published here:

* localhost/private addresses;
* temporary preview deployments;
* branch-preview URLs;
* `*.pages.dev` or `*.workers.dev` hosts;
* a reserved subdomain that has not actually been deployed.

## Reset and breaking-change policy

Exliquid is still in a pre-release stage. A new testnet generation may reset simulated balances or reject older signed transaction formats.

When that happens, this page should state clearly:

* which network is current;
* whether balances/history were reset;
* which SDK versions are supported;
* whether clients must update signing or API behavior.

See [Protocol identifiers](/docs/reference/protocol-identifiers.md) for the current signing-related identifiers.


---

# 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/reference/networks-and-versions.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.