Bech32 Encoded Tx Position References

The five-minute read

One action, walked through

1. Open BIP 136 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: A '''confirmed transaction position reference''', or '''TxRef''', is a reference to a particular location within the blockchain, specified by the block height and a transaction index within the block, and optionally, an outpoint index within the transaction.
3. Name the object that changes: Bech32 Encoded Tx Position References.
4. Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

The argument, unpacked

What has to be true

• You are implementing BIP 136 at the status the text itself states: Draft.
• The object that has to change is Bech32 Encoded Tx Position References. A neighbouring document with a similar name is not this one.
• Status in the header is not adoption.

What happened after the paper

The source marks this draft. It is not a live consensus rule just because it has a number. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• What must an implementation of Bech32 Encoded Tx Position References accept, and what may it ignore?
• Is this consensus, peer policy, or an application interface?
• Which names does the text pin down: Bech32 Encoded Tx Position References?

Terms

BIP 136

The public text titled Bech32 Encoded Tx Position References.

Draft

The document's own label for how finished the text is. It is not a market fact.

The problem the paper names

An interface that is only a name in a repository will be re-implemented differently by every team, which is how shared contracts break.

What the design proposes

• A '''confirmed transaction position reference''', or '''TxRef''', is a reference to a particular location within the blockchain, specified by the block height and a transaction index within the block, and optionally, an outpoint index within the transaction.
• ''Please Note: All values in this specification are encoded in little-endian format.''.
• The normative names to look up in BIP 136 are Bech32 Encoded Tx Position References.

How the mechanism is specified

• Taken from the specification, the next constraint is: ''Please Note: All values in this specification are encoded in little-endian format.''.
• Locate Bech32 Encoded Tx Position References in BIP 136 and apply it to one transaction or call.
• Then check the failure the class of rule always has: a node that did not upgrade, a reverted call, a replayed signature, or a peer that does not speak the message.

What this page does not treat as proven

• This document does not set a fee, a valuation, or a security proof.
• Status in the header is not adoption.
• The source marks this draft. It is not a live consensus rule just because it has a number.

Why a venture studio still reads it

Use BIP 136 when a pitch says 'Bech32 Encoded Tx Position References' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.