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

# Release notes

Release notes describe changes that matter to Exliquid users and integration developers.

A public release note should focus on:

* network availability or reset events;
* new or changed trading behavior;
* REST or WebSocket contract changes;
* supported SDK versions;
* signing or compatibility changes;
* new public endpoints or application surfaces;
* important security or operational notices that affect users;
* known limitations and breaking changes.

## Compatibility first

If a release requires an SDK upgrade, network reset, new signing domain or API migration, state that near the top of the release note with the required client action.

## What does not belong here

Public release notes should not mirror internal build pipelines, deployment scripts, evidence-bundle formats, private infrastructure changes or implementation-only refactors unless they change an external contract.

## Current status

No production mainnet release is declared by this page.

The current network availability and supported client contract are maintained in [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/releases.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.