> For the complete documentation index, see [llms.txt](https://docs.aeternity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aeternity.com/developer-documentation/aeternity/docs/release-notes/release-notes-5.2.0.md).

# About this release

[This](https://github.com/aeternity/aeternity/releases/tag/v5.2.0) is a maintenance Lima release\
focused on stability:

* SC clients will now receive a token which will be required for reestablishing a channel or\
  reconnecting to an existing FSM, the token must be persisted and kept secret by the client.
* Removes the user provided password from the state channel API
* Removes the special channel reconnect transaction -\
  reestablishing a channel may now result in reconnecting to an existing FSM
* This release ships with backwards incompatible changes to the client WS API.\
  Make sure a compatible SDK version is used when using state channels. Existing users of SC should\
  close their pre v5.2.0 channels and reopen them after v5.2.0. After v5.2.0 reconnection requests won't\
  require signing a transaction.
* Add database write retry logic, to prevent immediate failure during temporary\
  disk issues. The number of retries can be configured in the user configuration.
* Avoid JSON-encoding errors by sending oracle query/response format as `contract_bytearray` also\
  for `ABI_FATE_SOPHIA_1` in `/oracles/{pubkey}` HTTP API endpoint.
* Adds periodical log of number of connected peers
* Adds the number of connected peers (inbound and outbound) to HTTP /status endpoint

Please join the **mainnet** by following the instructions in the documentation below,\
and let us know if you have any problems by [opening a ticket](https://github.com/aeternity/aeternity/issues).\
Troubleshooting of common issues is documented [in the wiki](https://github.com/aeternity/aeternity/wiki/Troubleshooting).

## Documentation

For an overview of the installation process for different platforms,\
building the package from source, configuration and operation of the Aeternity\
node please refer to [Aeternity node documentation](https://docs.aeternity.io/).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aeternity.com/developer-documentation/aeternity/docs/release-notes/release-notes-5.2.0.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.