Best Practices for Heterogeneous Input Script Transactions

The five-minute read

One action, walked through

1. Open BIP 126 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: When a Bitcoin transaction contains inputs that reference previous transaction outputs sent to different Bitcoin addresses, personally identifiable information of the user will leak into the blockchain in an uncontrolled manner.
3. Name the object that changes: Best Practices for Heterogeneous Input Script Transactions.
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 126 at the status the text itself states: Draft.
• The object that has to change is Best Practices for Heterogeneous Input Script Transactions. 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 Best Practices for Heterogeneous Input Script Transactions accept, and what may it ignore?
• Is this consensus, peer policy, or an application interface?
• Which names does the text pin down: Best Practices for Heterogeneous Input Script Transactions?

Terms

BIP 126

The public text titled Best Practices for Heterogeneous Input Script Transactions.

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

• When a Bitcoin transaction contains inputs that reference previous transaction outputs sent to different Bitcoin addresses, personally identifiable information of the user will leak into the blockchain in an uncontrolled manner.
• While undesirable, these transactions are frequently unavoidable due to the natural fragmentation of wallet balances over time.
• This document proposes a set of best practice guidelines which minimize the uncontrolled disclosure of personally identifiable information by defining standard forms for transactions containing heterogeneous input scripts.

How the mechanism is specified

• Taken from the specification, the next constraint is: While undesirable, these transactions are frequently unavoidable due to the natural fragmentation of wallet balances over time.
• Locate Best Practices for Heterogeneous Input Script Transactions in BIP 126 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 126 when a pitch says 'Best Practices for Heterogeneous Input Script Transactions' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.