BA-12 · LESSON 07

Policy and resource debates

KEY DEFINITIONS

Terms used in this lesson

UTXO: Unspent transaction output: one discrete chunk of bitcoin that can be used as a transaction input.
Witness: Signatures, scripts, or other data supplied to satisfy a Bitcoin output’s spending condition.
OP_RETURN: A Bitcoin Script operation commonly used to create an unspendable output carrying a small amount of data.
CPU: Central processing unit: the general-purpose processor that performs validation and other software work.

Data protocols affect fees, relay policy, UTXO growth, miner incentives, and social arguments about block-space use.

55 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
COMMITPolicy and resource debates
The Policy and resource debates 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, Policy and resource debates. The Policy and resource debates 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 transaction spends one 50,000-sat input to two outputs of 20,000 and 25,000 sats. Both outputs have 22-byte scripts, and the input carries one 100-byte witness item.

MECHANISM

Calculate transaction weight, non-witness and witness composition, created UTXOs, long-term storage, bandwidth, and validation work.

AFTER

Block weight, actual fee, serialized history, local relay, and UTXO growth are separate properties and should not be conflated.

Text equivalent: Starting from A transaction spends one 50,000-sat input to two outputs of 20,000 and 25,000 sats. Both outputs have 22-byte scripts, and the input carries one 100-byte witness item. The mechanism begins when Calculate transaction weight, non-witness and witness composition, created UTXOs, long-term storage, bandwidth, and validation work. The resulting lesson is Block weight, actual fee, serialized history, local relay, and UTXO growth are separate properties and should not be conflated.

2. Mechanism pathSelect a stage to inspect its job

STAGE 1 OF 5

Measure resource use

Calculate transaction weight, non-witness and witness composition, created UTXOs, long-term storage, bandwidth, and validation work.

Complete path: 1. Measure resource use: Calculate transaction weight, non-witness and witness composition, created UTXOs, long-term storage, bandwidth, and validation work. 2. Apply policy boundaries: Nodes choose mempool relay policies within consensus. Miners can include consensus-valid transactions received through other channels. 3. Model fee competition: Users bid for limited block weight. Additional demand can raise fees, miner revenue, and confirmation delay for lower bids. 4. Separate externalities: Archived block data, initial sync, UTXO set growth, bandwidth bursts, and CPU cost burden different operators differently. 5. State value judgments explicitly: Consensus cannot measure whether one valid use is socially worthy. Proposals to filter or change limits should name technical effects, circumvention, and coordination risk.

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

ACCEPTED PATH

The serializer derives stripped bytes, witness bytes, weight, ceiling virtual size, input-minus-output fee, fee-rate eligibility, block-weight eligibility, and created-minus-spent UTXO delta independently.

CHANGED CONDITION

An overweight or underpriced candidate can lose miner selection without changing every consensus rule; local carrier filtering cannot redefine block validity, and a social-value claim is outside consensus arithmetic.

Important distinction: Every byte stored in a Bitcoin block permanently enlarges the UTXO set. The UTXO set tracks unspent spendable outputs. Witness and OP_RETURN data remain historical block data but do not each create UTXO entries.

Text equivalent: The accepted path is enforced by The serializer derives stripped bytes, witness bytes, weight, ceiling virtual size, input-minus-output fee, fee-rate eligibility, block-weight eligibility, and created-minus-spent UTXO delta independently. If the required condition changes, An overweight or underpriced candidate can lose miner selection without changing every consensus rule; local carrier filtering cannot redefine block validity, and a social-value claim is outside consensus arithmetic.

Loading lesson visuals...

Learn the idea

Bitcoin block space is scarce validation and propagation capacity allocated through fees and miner selection. A virtual byte, abbreviated vB, is transaction weight rounded up after division by four; vsize means that virtual size. Data-heavy protocols can increase fee demand and witness use. UTXO growth occurs only when transactions create spendable outputs that remain unspent; OP_RETURN data does not enter the UTXO set. Relay policy, consensus limits, miner incentives, and social preferences are separate parts of the debate.

GUIDED EXPLANATION1/5 ideas inspected

Measure resource use

Calculate transaction weight, non-witness and witness composition, created UTXOs, long-term storage, bandwidth, and validation work.

The worked example follows the explanation

Inspect every idea above to open it.

Important distinction“Every byte stored in a Bitcoin block permanently enlarges the UTXO set.”

The UTXO set tracks unspent spendable outputs. Witness and OP_RETURN data remain historical block data but do not each create UTXO entries.

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.