BA-12 · LESSON 04

Indexer consensus

Meta-protocol users depend on deterministic off-chain interpretation and must understand divergence and reorg handling.

65 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
COMMITIndexer consensus
The Indexer consensus 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, Indexer consensus. The Indexer consensus 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

At height 500, parser A treats unknown tag 9 as ignorable; parser B classifies it as a burn.

MECHANISM

Record implementation version, activation points, feature flags, network, and canonical test vectors before comparing outputs.

AFTER

Chain agreement is necessary but not sufficient for metaprotocol agreement.

Text equivalent: Starting from At height 500, parser A treats unknown tag 9 as ignorable; parser B classifies it as a burn. The mechanism begins when Record implementation version, activation points, feature flags, network, and canonical test vectors before comparing outputs. The resulting lesson is Chain agreement is necessary but not sufficient for metaprotocol agreement.

2. Mechanism pathSelect a stage to inspect its job

STAGE 1 OF 5

Pin protocol rules

Record implementation version, activation points, feature flags, network, and canonical test vectors before comparing outputs.

Complete path: 1. Pin protocol rules: Record implementation version, activation points, feature flags, network, and canonical test vectors before comparing outputs. 2. Read one accepted chain: Indexers process transactions in block and transaction order from a fully validated or clearly trusted chain source. 3. Apply deterministic transitions: Every message either updates derived state, is ignored, or triggers defined invalid behavior. Error recovery must not depend on local arrival timing. 4. Checkpoint and compare: State roots, balances, object counts, and per-block transition logs help independent implementations locate their first divergence. 5. Rollback reorgs: On block disconnection, reverse derived transitions exactly, then replay the replacement branch under the same rules.

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

ACCEPTED PATH

Network, inclusive activation height, parser version, invalid-message rule, canonical event order, state transition, and full ordered root are pinned before derived state changes.

CHANGED CONDITION

Pre-activation, wrong-network, or wrong-version events do not mutate the index; parser disagreement changes the first action or root, and a reorg must disconnect the old suffix before replacement replay.

Important distinction: If indexers follow the same Bitcoin node, they must have identical application state. Different parsing, versions, bugs, activation settings, or rollback logic can derive different states from identical valid bytes.

Text equivalent: The accepted path is enforced by Network, inclusive activation height, parser version, invalid-message rule, canonical event order, state transition, and full ordered root are pinned before derived state changes. If the required condition changes, Pre-activation, wrong-network, or wrong-version events do not mutate the index; parser disagreement changes the first action or root, and a reorg must disconnect the old suffix before replacement replay.

Loading lesson visuals...

Learn the idea

Indexer consensus is informal shorthand for independent indexers producing the same derived metaprotocol state. They do not create Bitcoin consensus. Agreement requires identical network identity, parser versions, inclusive activation heights, transaction ordering, invalid-message behavior, and reorg rollback. A pre-activation, wrong-network, or unsupported-version event must not mutate the pinned index. A divergence can show different balances while every indexer follows the same valid Bitcoin chain.

GUIDED EXPLANATION1/5 ideas inspected

Pin protocol rules

Record implementation version, activation points, feature flags, network, and canonical test vectors before comparing outputs.

The worked example follows the explanation

Inspect every idea above to open it.

Important distinction“If indexers follow the same Bitcoin node, they must have identical application state.”

Different parsing, versions, bugs, activation settings, or rollback logic can derive different states from identical valid bytes.

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.