> For the complete documentation index, see [llms.txt](https://dasus.gitbook.io/dasus-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dasus.gitbook.io/dasus-docs/the-app/announcements.md).

# Announcements

**Announcements** is the public log of what changed on Dasus and on the markets it lists: new listings, delistings, updates, maintenance and general notices, most recent first. It lives at `/announcements` (navbar → **More** → **Announcements**) and needs no wallet.

## Reading the page

Four tabs with counts — **All announcements · Listings · Delistings · Updates** (Updates groups updates, maintenance and info) — and the number of items in view. Each row shows its date, a type label, the title and, when there is one, a short body:

| Type            | Meaning                                                        |
| --------------- | -------------------------------------------------------------- |
| **Listing**     | A market that is now live on Hyperliquid and tradable on Dasus |
| **Delisting**   | A market Hyperliquid has retired; it is no longer tradable     |
| **Update**      | A change to the platform                                       |
| **Maintenance** | Planned work or a temporary limitation                         |
| **Info**        | Anything else worth knowing                                    |

Items under seven days old carry a **New** tag. When an announcement has a link — a new market's trade page, for instance — the whole row is the link. The list shows 40 at a time; **Show more** loads the next 40. The page refreshes itself every couple of minutes.

## Where else announcements appear

* **On-screen cards** (bottom-right) for **one hour** after an announcement is published, on every screen except the landing, legal and admin pages. Close one with the X and it stays closed in that browser; after the hour it disappears by itself.
* **A banner strip** on certain pages such as Portfolio, when Dasus chooses to promote a notice that way, with an optional validity window and call-to-action. You can dismiss it; it comes back only if the notice is edited.

The page is the full history; the cards and the banner are just the recent slice of the same feed.

## Where listings and delistings come from

Dasus compares Hyperliquid's live universe — perpetuals on the main book and on every HIP-3 dex, plus spot pairs — against its last snapshot roughly every 15 minutes while the app is in use. A market that appears is drafted as a **Listing**, and a market Hyperliquid flags as delisted is drafted as a **Delisting**; both are published once Dasus approves them. If an entire dex appears at once, only the first ten markets are announced in that sweep to avoid flooding the feed. Updates, maintenance and info notices are written by Dasus.

{% hint style="info" %}
A listing here means the market exists on the protocol and can be traded through Dasus. It is not a recommendation, and Dasus does not review the projects behind HIP-3 or spot listings. The spot list you see by default is curated separately — see [Spot Trading](https://dasus.gitbook.io/dasus-docs/trading/spot.md).
{% endhint %}

## Related pages

* [Markets](https://dasus.gitbook.io/dasus-docs/market-data-and-research/markets.md) — the live catalogue of everything tradable
* [Spot Trading](https://dasus.gitbook.io/dasus-docs/trading/spot.md) — how the spot list is curated (Strict list vs. All)


---

# 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://dasus.gitbook.io/dasus-docs/the-app/announcements.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.
