Protocol Lab

What the lab is and is not

The lab replays protocol rules deterministically so you can see why units land where they land. It never asks for keys, never signs, and never broadcasts. Every identifier it generates is synthetic, derived from the scenario seed, and starts with “sim”.

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.

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

Run edited scenario Import file

Share and export

Copy shareable link Scenario JSON Execution trace

Run scenario Reset Load a scenario to begin.

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.

Share and export

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.