> 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/protocol-identifiers.md).

# Protocol identifiers

This page records identifiers that external clients need for network selection, signing and transaction construction.

{% hint style="warning" %}
These values identify the current pre-release testnet lineage. They do not mean the public testnet endpoint is open.
{% endhint %}

## Current client identifiers

| Identifier               | Current value               |
| ------------------------ | --------------------------- |
| Chain ID                 | `exliquid-public-testnet-5` |
| EIP-712 numeric chain ID | `9559005`                   |
| Signing/network domain   | `exliquid/public-testnet`   |
| REST contract            | `/api/v1`                   |
| WebSocket contract       | `/ws/v1`                    |

## Nonce domains

The current signing contract defines distinct nonce domains for different classes of action:

| Domain       | Value | External purpose                         |
| ------------ | ----: | ---------------------------------------- |
| Trading      |   `1` | Ordinary trading actions                 |
| Privileged   |   `2` | Authorized control actions where exposed |
| Risk control |   `3` | Restricted rescue/reduce-risk actions    |

A client must query and increment the nonce for the correct account, signer, subaccount and domain.

The risk-control domain is not a general second trading lane; only actions permitted by the current transaction contract can use it.

## Transaction identifiers

Transaction IDs identify signed Exliquid transactions and are used for lookup and confirmation.

Clients should retain the transaction ID until the outcome is known and use the transaction/confirmation endpoints rather than inventing an identifier from an HTTP request.

## Compatibility

Network and signing identifiers are validation inputs.

A client must not silently submit a transaction signed for another Exliquid testnet generation or incompatible API/protocol contract.

For supported SDK versions and public endpoints, always pair this page with [Networks and versions](/docs/reference/networks-and-versions.md).


---

# 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/protocol-identifiers.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.