Networks and versions

Three separate version axes affect every source-sensitive statement on this site. Mixing them up is the single most common cause of wrong integrations.

Pinned source revisions used across this documentation

Source	Authority	Revision	Networks	Visibility
Atomicals ElectrumX Version-sensitive ARC-20 and Atomicals validation behavior used as the pinned reference baseline.	Protocol	v1.5.2.0	mainnet	public
Atomicals JavaScript CLI Reference command surface used for the documented CLI inventory and the visual asset provenance.	Protocol	1333565efbfe	mainnet, testnet, regtest	public
Atomicals protocol guide Concept and command-line explanation. Explicitly states that the specification is defined in code.	Protocol	unversioned	mainnet	public
Atomicals Improvement Proposals The AIP register. An AIP existing is not evidence that anything implements it.	Protocol	be08d7856db7	mainnet	public
Universe ARC-20 index and Marketplace v1 authority Universe ARC-20 token explorer feed and the durable Marketplace v1 protocol authority.	Universe	670030e50071	mainnet	private
Universe Atomicals NFT, Realm, and Subrealm index Materialized read model for plain NFTs, Realms, and Subrealms projected from Atomicals ElectrumX.	Universe	1d9109c68d95	mainnet	private
Ordex marketplace contract Marketplace OpenAPI contract, SDK, conformance vectors, and purchase verifier reused instead of restated here.	Universe	2f7d8d3ec59f	mainnet	public
Bitcoin Inscribe Product surface that consumes this documentation as the frontend/docs/arc-20-docs submodule.	Universe	unversioned	mainnet	private
Atomicals Virtual Machine interpreter Beta AVM interpreter. Status layer is separate from any Universe runtime exposure.	Protocol	c185e6216a3e	not deployed	public
Ordinals and Runes reference indexer (ord) Comparative context only. The ord indexer defines Ordinals inscription tracking and the Runes ledger used in the Protocol Atlas.	Protocol	899e309424dd	mainnet	public
BRC-20 experiment specification (domo) Comparative context only. The original BRC-20 rule text. Indexer implementations diverge, so behavior is implementation-specific.	Universe	unversioned	mainnet	public
Bitcoin Stamps and SRC-20 reference indexer Comparative context only. Reference indexer for Stamps and SRC-20 used in the Protocol Atlas.	Universe	8a7365bf951a	mainnet	public
Alkanes and Protorunes reference implementation Comparative context only. Reference Rust implementation of the Alkanes metaprotocol and Protorunes tokens.	Universe	62511e9371a3	mainnet	public
Counterparty reference library Comparative context only. Reference implementation of the Counterparty ledger used in the Protocol Atlas.	Universe	4f39fe25a266	mainnet	public
RGB core consensus library Comparative context only. Client-side validation consensus library for RGB used in the Protocol Atlas.	Universe	388d9c386117	mainnet	public

1. The network

Atomicals activation conditions are network specific. The pinned reference implementation carries different activation heights per coin definition. A rule that is active on mainnet may be inactive, active at a different height, or always-on in a regtest configuration.

Every page lists the networks it applies to in its source panel. When a page says mainnet only, do not assume the same behavior elsewhere.

2. The validator revision

The Atomicals specification is defined in code. The reference revision this documentation is pinned to is Atomicals ElectrumX 8df23747, released as v1.5.2.0 on 2025-03-27.

That revision is preserved as a stable historical baseline. It is not silently rewritten when a Universe service upgrades. Universe implementation revisions are listed separately, per page, in the source panel.

Two indexers can disagree and both be right

If two implementations at different revisions read the same transaction differently, that is a version difference, not a bug in one of them. Investigate the revision and activation state before deciding which answer to trust. Never resolve a disagreement by majority vote.

3. The documentation version

This site publishes documentation version 2026.08. Each page states the version it describes in its source panel. See versions and compatibility for the full matrix, and releases for what changed.

How to pin your own integration

1. Choose an Atomicals validator revision or release, and record it.
2. Record the network and its active rule set.
3. Record the Universe service revision if you consume our APIs. Every service exposes it on GET /version.
4. Re-run the conformance vectors against that exact combination.
5. Re-check before every upgrade, not after.

What “activation” means here

An activation boundary is a block height or configuration flag that turns a validation rule on. Before the boundary the old interpretation applies. After it the new one does. A transaction is judged by the rules active at its own height, not by today’s rules.

Pages that describe activation-sensitive behavior show the boundary in the source panel under Activation boundary. See activation boundaries.