BA-12 · LESSON 02

Ordinals and inscriptions

KEY DEFINITIONS

Terms used in this lesson

Witness: Signatures, scripts, or other data supplied to satisfy a Bitcoin output’s spending condition.
Taproot: A Bitcoin output and spending design that can combine a public-key path with privately committed alternative scripts.
Control block: Proof data showing that a revealed script was committed inside a Taproot output.
Tapscript: The version of Bitcoin Script used by a Taproot script-path spend.
BIP341: The Bitcoin Improvement Proposal specifying Taproot output validation and the transaction signature message used by Taproot signatures.
Sighash: The exact transaction digest and signature mode that determine which fields a Bitcoin signature authorizes.
OP_FALSE: A Bitcoin Script operation that pushes false; inscription envelopes commonly combine it with OP_IF so their data branch is not executed.
OP_IF: A Bitcoin Script conditional operation that executes one branch when the consumed condition is true.

Ordinal theory assigns ordering conventions to satoshis while inscriptions use witness envelopes interpreted by off-chain indexers.

45 min Difficulty 3/5 Not started

VISUAL MODEL

See the whole mechanism before going step by step

Use the diagrams to orient yourself. Then the guided explanation below teaches every part in depth.

4 explanatory views

CONCEPT-SPECIFIC MAP · data commitmentExternal meaning is anchored to exact Bitcoin bytesSelect any state to inspect its exact role.

RELATIONSHIP MAPOrdered validation pipeline

01
PAYLOADTyped external meaning
An application defines a payload, event, inscription, or token instruction.
02
ENCODECanonical bytes
Ordering, lengths, tags, and version rules must be unambiguous.
03
COMMITOrdinals and inscriptions
The Ordinals and inscriptions mechanism places or commits those bytes in a Bitcoin transaction.
04
BITCOINValid transaction
Bitcoin nodes enforce only Bitcoin consensus rules for the carrier transaction.
05
INDEXReconstructed state
Application software scans the chain and applies its own versioned state-transition rules.

Rule shown: Bitcoin validates transaction bytes and Script; indexers apply additional protocol meaning deterministically.

STAGE 1 OF 5PAYLOAD: Typed external meaning

An application defines a payload, event, inscription, or token instruction.

Governing relationship: Bitcoin validates transaction bytes and Script; indexers apply additional protocol meaning deterministically. Complete path: 1. PAYLOAD, Typed external meaning. An application defines a payload, event, inscription, or token instruction. 2. ENCODE, Canonical bytes. Ordering, lengths, tags, and version rules must be unambiguous. 3. COMMIT, Ordinals and inscriptions. The Ordinals and inscriptions mechanism places or commits those bytes in a Bitcoin transaction. 4. BITCOIN, Valid transaction. Bitcoin nodes enforce only Bitcoin consensus rules for the carrier transaction. 5. INDEX, Reconstructed state. Application software scans the chain and applies its own versioned state-transition rules.

1. State transitionWhat exists, what changes, and what results

BEFORE

A Taproot commit fixes a bounded OP_FALSE OP_IF ord envelope. Its reveal spends one 1,000-sat input into output A of 500 sats and output B of 450 sats, with a 50-sat fee. The…

MECHANISM

The indexer orders newly issued and transferred satoshis under its specified first-in-first-out tracking convention.

AFTER

Bitcoin validates the committed spend; ordinal location and envelope meaning are deterministic external interpretations that must roll back with the active chain.

Text equivalent: Starting from A Taproot commit fixes a bounded OP_FALSE OP_IF ord envelope. Its reveal spends one 1,000-sat input into output A of 500 sats and output B of 450 sats, with a 50-sat fee. The inscribed offset is 720. The mechanism begins when The indexer orders newly issued and transferred satoshis under its specified first-in-first-out tracking convention. The resulting lesson is Bitcoin validates the committed spend; ordinal location and envelope meaning are deterministic external interpretations that must roll back with the active chain.

2. Mechanism pathSelect a stage to inspect its job

STAGE 1 OF 5

Assign ordinal positions

The indexer orders newly issued and transferred satoshis under its specified first-in-first-out tracking convention.

Complete path: 1. Assign ordinal positions: The indexer orders newly issued and transferred satoshis under its specified first-in-first-out tracking convention. 2. Commit reveal data: An inscription workflow creates a Taproot commitment, then a reveal spend exposes a witness script containing a recognizable envelope and content bytes. 3. Validate Bitcoin normally: Nodes verify the transaction, Taproot commitment, Script, weight, and fees. They do not run ordinal numbering as consensus. 4. Parse the envelope: Compatible indexers scan witness data for the protocol marker, content type, fields, and body, then associate it under ordinal rules. 5. Track later transfers: The indexer follows the inscribed satoshi through input and output value ranges, including fees and reorg rollback.

3. Rule and failure boundaryWhat accepts the result and where it can stop

ACCEPTED PATH

The reveal must conserve value, authorize the bounded Script, reconstruct the committed Taproot output key, contain a complete envelope, map the sat offset, and remain on the active branch.

CHANGED CONDITION

A wrong control block, bad authorization, malformed envelope, fee-range offset, or disconnected reveal prevents or relocates derived inscription state; a valid replacement branch replays it.

Important distinction: Bitcoin consensus marks particular satoshis as inscriptions. Consensus treats satoshis as fungible amounts. Ordinal-aware indexers add numbering and inscription interpretation from committed transaction data.

Text equivalent: The accepted path is enforced by The reveal must conserve value, authorize the bounded Script, reconstruct the committed Taproot output key, contain a complete envelope, map the sat offset, and remain on the active branch. If the required condition changes, A wrong control block, bad authorization, malformed envelope, fee-range offset, or disconnected reveal prevents or relocates derived inscription state; a valid replacement branch replays it.

Loading lesson visuals...

Learn the idea

Ordinal theory is an off-chain convention that numbers satoshis and tracks their movement through transactions. An inscription places content in a Taproot witness envelope that ordinary Bitcoin consensus treats as executed or skipped Tapscript data. An indexer applies ordinal and envelope parsing rules to assign that content to a satoshi. BIP341 is the Bitcoin Improvement Proposal that specifies Taproot output and script-path validation. The in-app workbench builds real TapLeaf and TapBranch hashes, reconstructs the output key from a control block, executes a bounded owner-signature Script over the exact revealed script, parses the bounded inscription envelope, tracks the satoshi through outputs and fees, and rolls derived state back during a reorganization. The owner signature uses a teaching digest of the revealed script, not a BIP341 transaction sighash, and the complete Ordinals grammar remains outside this fixture.

GUIDED EXPLANATION1/5 ideas inspected

Assign ordinal positions

The indexer orders newly issued and transferred satoshis under its specified first-in-first-out tracking convention.

The worked example follows the explanation

Inspect every idea above to open it.

Important distinction“Bitcoin consensus marks particular satoshis as inscriptions.”

Consensus treats satoshis as fungible amounts. Ordinal-aware indexers add numbering and inscription interpretation from committed transaction data.

FINISH LEARNING FIRST

The questions unlock after every required learning activity

Inspect every guided idea, open the worked example, rebuild its mechanism, and complete the deterministic lesson tool. Your progress is saved automatically.