> ## Documentation Index
> Fetch the complete documentation index at: https://visualsign.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

> Curated release notes for VisualSign — one stream per chain plus a core stream, versioned by release.

Pick the stream that matters to you. Each stream has its own RSS feed.

> [card] [Solana](https://visualsign.dev/changelog/solana.md)
>
> Solana preset coverage, IDL handling, decoder fixes.

> [card] [Ethereum](https://visualsign.dev/changelog/ethereum.md)
>
> EVM protocol decoders, ABI registry changes, contract additions.

> [card] [Sui](https://visualsign.dev/changelog/sui.md)
>
> Sui Move package decoders, programmable transactions.

> [card] [Tron](https://visualsign.dev/changelog/tron.md)
>
> Tron contract decoders, TRC standards.

> [card] [NEAR](https://visualsign.dev/changelog/near.md)
>
> NEAR transaction decoding, the NEAR Intents preset, signature verification.

> [card] [Core](https://visualsign.dev/changelog/core.md)
>
> Core types, field builders, HTTP/gRPC API, attestation, policy, build and test infrastructure.

## How releases are tagged

Tags are auto-cut from `main` by the release workflow. The `description` on each `<Update>` block points to the first release that contains the change. If you pull a tag at or above that version, the change is in.

## How entries are authored

Contributors drop a draft fragment in `docs/changelog/_drafts/` on the PR that ships the change. A maintainer batches drafts into one or more `<Update>` blocks at curation time, splits them across the per-chain and core pages by category, and deletes the consumed drafts. See [`docs/changelog/_drafts/README.md`](https://github.com/anchorageoss/visualsign-parser/blob/main/docs/changelog/_drafts/README.md) for the format.

## Tag vocabulary

All streams use a shared controlled tag vocabulary so RSS subscribers can filter:

* **Audience** — `Wallet API`, `Contributors`, `Security`, `Ecosystem`.
* **Theme** — `Policy`, `Architecture`, `Lints`, `Attestation`, `Performance`.

Chain pages do not use a chain tag (the page already conveys the chain).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.