> For the complete documentation index, see [llms.txt](https://docs.onchainradar.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onchainradar.ai/welcome/updates-history.md).

# Updates History

Здесь мы публикуем историю развития **Onchain Radar** — новые релизы, функции, скринеры и ключевые изменения платформы.

<details>

<summary>Onchain Radar v.1.0 - 27.08.2026</summary>

**Первый публичный релиз Onchain Radar.**

Мы запустили первую версию платформы, объединив основные инструменты для поиска и анализа ончейн-данных в одном интерфейсе.

### Скринеры

На момент запуска в Onchain Radar доступно **15+ скринеров**, разделённых на несколько направлений.

Hyperliquid Screeners

* Positions
* TWAPs
* Liquidation Risk
* Avg Entry

Wallets Screeners

* Smart Wallets
* Wallet Flows
* Team Wallets

Token Events Screeners

* Claims
* Burns
* Token Unlocks

DEX CEX Screeners

* Price change
* DEX Volume
* DEX Spikes

Arbitrage Screeners

* Spreads

#### Alerts

Запустили систему уведомлений, которая позволяет получать информацию о важных ончейн-событиях без необходимости постоянно следить за скринерами вручную.

</details>


---

# 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://docs.onchainradar.ai/welcome/updates-history.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.