Protocol Lab

Construct and replay Atomicals workflows deterministically in the browser, with no keys, no signing, and no network.

Protocol behavior Verified 2026-09-02 Metadata & Sources

Describes the Atomicals protocol itself at the pinned reference revision. It does not promise that any product exposes it.

Page ID

tools/protocol-lab

Normative authority

Executed source code at a pinned revision

Networks

regtest, testnet, signet, mainnet

Documentation version

2026.08

Audience

everyone, developer, holder, creator

Owner

bitcoin-universe-docs

Sources

Atomicals ElectrumX at v1.5.2.0 the allocation rules every transfer scenario executes

Known limitations

Scenarios are deterministic models. Identifiers are synthetic and derived from the scenario seed; they are not real Bitcoin hashes.
The lab models normal ARC-20 allocation, commit and reveal, confirmations, and reorganizations. It does not simulate semantics the pinned reference does not support.
Nothing here substitutes for validating a concrete transaction against the validator revision you target.

本頁內容尚未翻譯。

Pick a guided scenario, watch each step apply the shared rules, and click a rule to open the exact page that explains it. The same allocation module executes the conformance vectors, powers the allocation visualizer, so the lab cannot disagree with them.

The scenario library, JSON editor, and trace render below when JavaScript runs. Without it, read the scenario sources in packages/protocol-lab/scenarios and the rule pages they cite.

Everything here runs offline in your browser against the shared allocation engine. Scenarios are synthetic: identifiers start with "sim" and are derived from the scenario seed. Nothing is ever signed, broadcast, or uploaded.

Scenario library

Scenario JSON

Edit raw scenario

Scenario JSON, validated before it runs

Share and export

What the scenarios cover

Commit and reveal for NFTs, Realms, and ARC-20 deployments and mints.
ARC-20 transfer, split, and merge through the reference allocation engine.
Intentional burns to unspendable outputs, and the accidental burn pattern that destroys units.
Confirmation progression and a one-block reorganization that unsettles confirmed state.
An invalid operation the engine refuses instead of inventing money.

Every scenario is data. Copy a shareable link for a small scenario, or export the scenario JSON and the execution trace as files. Large scenarios stay local by design: nothing is ever uploaded anywhere.

Where the rules come from

The engine lives in packages/protocol-lab and calls the allocation engine in packages/protocol-core, which is the exact module the conformance vectors execute at the pinned reference revision. Each trace entry names the rule it evaluated and the outcome.

本頁面的來源