Bitcoin-native digital objects and fungible units

Atomicals, explained from source to execution.

Version-pinned protocol documentation, deterministic labs, API conformance, safe UTXO planning and agent-ready workflows for ARC-20, NFTs, Realms, Containers, DMINT and AVM.

Start building Open Protocol Lab Inspect the sources

One satoshi, from UTXO to object. A single satoshi can be plain bitcoin, an ARC-20 unit, or a non-fungible Atomical. Creating an Atomical follows two steps: a commit pays to a Taproot output, then a reveal spends it. The object is assigned to output zero of the reveal, and nothing exists before that reveal.

One satoshi, from UTXO to object

A single satoshi can be plain bitcoin, an ARC-20 unit, or a non-fungible Atomical. Creating an Atomical follows two steps: a commit pays to a Taproot output, then a reveal spends it. The object is assigned to output zero of the reveal, and nothing exists before that reveal.

Where the protocol stands today

Protocol baseline

Atomicals ElectrumX v1.5.2.0 (2025-03-27)

Documentation source set

2026.08

Sources verified

15 pinned sources, last verified 2026-08-31

Drift status

No upstream movement recorded at last check

Start where you are

• New hereNewcomers

  What an Atomical is, why one ARC-20 unit is one satoshi, and the safety rules that stop permanent burns.

• Ship an appApplication developers

  Read the API contracts, generate a typed client, validate your implementation against conformance vectors.

• Run the servicesIndexer operators

  Readiness, freshness, reorg handling, and what a degraded index actually means for callers.

• Question the claimsProtocol researchers

  Every rule traced to the pinned reference revision, with activation boundaries and known divergences.

• Bring a modelAI agents

  Stable page IDs, raw Markdown, llms.txt, source manifests, and a read-only MCP server.

Learn, simulate, verify, reproduce

One journey covers everything this platform does. Understand a rule in the protocol pages. Replay it deterministically in a browser tool. Check an implementation against the executed conformance vectors. Then reproduce the whole workflow yourself with the CLI and the pinned sources.

• Step 1Learn

  Protocol pages explain one rule at a time, each pinned to a source revision and a verification date.

• Step 2Simulate

  Browser tools replay allocation, splits, burns, and Bitwork search with no keys and no network.

• Step 3Verify

  Conformance vectors execute in CI. The prose, the tools, and the tests share one engine.

• Step 4Reproduce

  CLI reference and pinned source paths let you rerun every documented workflow locally.

Everything on the platform

• CompareProtocol Atlas

  Atomicals, ARC-20, Ordinals, Runes, BRC-20, Stamps, TAP, Alkanes, Counterparty, and RGB, every cell pinned to a source.

• SimulateProtocol Lab

  Replay commit and reveal, ARC-20 transfers, splits, burns, and reorganizations deterministically in your browser.

• Plan safelyUTXO Safety Planner

  Classify asset-bearing outputs, see the burn risks, and generate plans that preserve your units.

• Model unitsAllocation visualizer

  Model inputs and outputs and see exactly which units land where, and which burn.

• Read transactionsTransaction inspector

  Decode envelopes, operations, and PSBT structure from a raw transaction or hex payload.

• Plan mining costBitwork estimator

  Estimate the search effort a commit needs for a given prefix and charset.

• Compose commandsCLI builder

  Assemble atomicals-js CLI commands and read what each flag does before you run it.

• Read the contractsOffline API explorer

  Browse the OpenAPI operations, schemas, and examples entirely offline by default.

• ContractsOpenAPI and schemas

  Validated OpenAPI 3.1 documents, JSON Schemas, and a generated TypeScript client.

• EvidenceConformance vectors

  Deterministic vectors executed in CI. The visualizer and the prose share them.

• AgentsMCP server

  A local stdio MCP server exposes pages, manifests, and contracts to coding agents.

• TypeScriptClient SDK

  A typed read-only client generated from the same OpenAPI documents the site validates.

Why every claim carries a revision

This platform separates three things that other material blurs together:

Protocol behavior

What a pinned Atomicals validator does

Universe implementation

What our services expose today

Proposed or beta

What exists but is not live

A protocol capability is not automatically a product feature. Each page states which layer it describes, at which source revision, and when that was last checked. The context strip under the site header repeats it on every page, and the drawer behind it opens the exact source paths.

Versions and verification

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 Improvement Proposals The AIP register. An AIP existing is not evidence that anything implements it.	Protocol	be08d7856db7	mainnet	public
Atomicals Virtual Machine interpreter Beta AVM interpreter. Status layer is separate from any Universe runtime exposure.	Protocol	c185e6216a3e	not deployed	public

See Versions for the full manifest and how drift is handled.

AVM is beta

The AVM interpreter material on this platform describes a pinned beta revision. Executing samples locally is supported. Nothing here is evidence of deployment by Bitcoin Universe, and no page will describe AVM as live or production-ready until a verified source set says so. Start at AVM overview.

Built for machines too

Every page has a raw Markdown twin, a stable page ID, and a source record. The site also publishes llms.txt, llms-full.txt, a page manifest, JSON Schemas, OpenAPI documents, and a read-only MCP server so an agent can read this documentation without scraping HTML.

See AI and agent access.

What we will not tell you

No price talk. No rankings. No investment, legal, or tax advice. No claim that a ticker proves who made something, that metadata proves authenticity, or that a marketplace listing proves ownership. Where evidence is missing, the page says so instead of guessing.