One verified source set exists. The navigator is ready for the next set the moment verified source material for it exists; it never fabricates a historical snapshot to make this selector look fuller.
Verified August 2026 baseline
currentverified 2026-08-31mainnet
Protocol baseline
atomicals-electrumx-1.5.2.08df23747835cAtomicals ElectrumX v1.5.2.0, the pinned reference validator behavior for ARC-20 and Atomicals rules.
CLI
atomicals-js-cli1333565efbfeThe JavaScript CLI the command inventory and CLI builder are generated from.
AIP registry
atomicals-aipsbe08d7856db7The AIP register snapshot. A proposal existing is not evidence that anything implements it.
Universe runtime
universe-index-atomicals670030e50071Universe ARC-20 index and Marketplace v1 authority.
AVM interpreter (beta)
atomicals-avm-interpreterc185e6216a3eBeta interpreter. Version isolation matters most here: nothing in this set describes AVM as deployed.
Documentation build
2026.08The documentation build that renders this source set.
API contracts
arc201.0.0
atomicals-nfts-realms1.0.0
marketplace-v11.0.0
Semantic changes between sets
Diffs are computed between verified sets only. Protocol rules, OpenAPI operations, JSON
Schemas, CLI commands, AIP states, source revisions, and compatibility declarations are
compared as added, removed, changed, status changed, source moved, or implementation
divergence.
No two verified sets exist to compare yet, so the change list is empty. When a second set is
verified the comparison appears here and at the machine-readable output below. A detected
upstream change shows as "upstream moved; current documentation remains pinned" and never
silently rewrites normative content.
BRC-20 experiment specification (domo) Comparative context only. The original BRC-20 rule text. Indexer implementations diverge, so behavior is implementation-specific.
Protocol reference baseline. Atomicals ElectrumX v1.5.2.0, commit 8df23747, released
2025-03-27. Every version-sensitive protocol statement on this site is pinned to it. It is not
silently updated.
Universe implementation revisions. Listed separately, per page, in each source panel. They move
with deployments.
The full platform: protocol, guides, contracts, tools, and machine readable outputs
Earlier documentation existed as a small set of standalone files. Those routes are preserved as
compatibility artefacts and are regenerated from this content, so they cannot drift.
See deprecations.