Releases
What changed in this documentation, when, and why, with the machine readable feed alongside.
Editorial Verified 2026-08-31
Navigation or explanatory writing with no source-sensitive claim of its own.
- Page ID
-
releases/index - Normative authority
- No normative source. Navigation only.
- Networks
- mainnet
- Documentation version
- 2026.08
- Audience
- everyone, developer, integrator
- Owner
- bitcoin-universe-docs
Documentation version 2026.08. The machine readable form of this page is the changelog feed.
2026.08 2026-08-31
Documentation platform
Replaced the hand-authored single-page site with a generated documentation platform covering the whole Atomicals protocol family, the Universe API contracts, executed conformance material, interactive safety tools, and machine readable outputs.
- added Complete protocol reference for Atomicals core concepts, ARC-20, Atomicals NFTs, Containers and DMINT, Realms, Subrealms, Paynames, and the AVM, each labelled by what it applies to and pinned to a source revision.
- added Thirty one task-oriented guides covering setup, inspection, issuance, minting, transfers, recovery, and trading, each with prerequisites, safety checks, failure cases, and post-broadcast verification.
- added Validated OpenAPI 3.1 documents for the ARC-20 index, the NFT and Realm index, and Marketplace v1, bound to sanitized route inventories by a check that fails in both directions.
- added A shared JSON Schema component library where every satoshi and protocol quantity is a decimal string, and every example is validated in CI.
- added Executed ARC-20 allocation conformance vectors and the engine behind them, implemented from the pinned reference revision and shared by the prose, the visualizer, and the tests.
- added A generated CLI inventory parsed from the pinned Atomicals JavaScript CLI source, covering every command, argument, and option.
- added A generated AVM opcode inventory parsed from the beta interpreter source, with the upstream test annotation preserved per opcode.
- added An AIP registry generated from the upstream proposals plus a separate implementation evidence file, so no proposal is ever marked implemented because it exists.
- added Interactive local tools: an allocation visualizer, a transaction safety inspector, a Bitwork estimator, a CLI command builder, and an API explorer. None signs, broadcasts, or sends anything anywhere.
- added An evidence-based ecosystem registry that records unknown rather than guessing, and never treats a network failure as closure.
- added Machine readable outputs: llms.txt, llms-full.txt, llms.html, a page manifest with content hashes, raw Markdown for every page, a sitemap, and a changelog feed.
- added A generated TypeScript client for the public read surfaces, with typed errors, pagination helpers, and no embedded credential or default origin.
- added A local, read-only documentation MCP server that answers from built artefacts, offline, with no mutation, signing, or credential capability.
- added Eight configured locales with a required page set, a shared glossary, a prohibited mistranslation list, and automatic staleness detection from the English source hash.
- restored The specification, source ledger, and LLM layer, now generated from the content rather than hand maintained, so the compatibility routes cannot drift from the current documentation.
- fixed The published site URL now agrees across repository metadata, README links, canonical tags, Open Graph metadata, the sitemap, and the Pages configuration.
What is versioned separately
Section titled “What is versioned separately”| Axis | Where it appears | Current |
|---|---|---|
| Protocol reference baseline | The pinned validator revision | Atomicals ElectrumX v1.5.2.0 |
| Universe API surface | The /v1/ segment and the service revision |
v1 |
| Marketplace contract | The Marketplace v1 route and signing contract | v1 |
| Generated schemas | A version field in each schema | 1.0.0 |
| Documentation | The version on every page | 2026.08 |
Never assume two of them move together. See versioning and deprecation.
Related
Section titled “Related”| Page | Contains |
|---|---|
| Versions and compatibility | Every pinned source revision and what it applies to |
| Deprecations | What is scheduled for removal, and what replaces it |
| Migrations | Step by step moves between versions |