Version bits with timeout and delay

The five-minute read

One action, walked through

1. Open BIP 9 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: This document specifies a proposed change to the semantics of the 'version' field in Bitcoin blocks, allowing multiple backward-compatible changes (further called "soft forks") to be deployed in parallel.
3. Name the object that changes: Version bits with timeout and delay.
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 9 at the status the text itself states: Deployed.
• The object that has to change is Version bits with timeout and delay. A neighbouring document with a similar name is not this one.
• Wallet support is not the same as consensus validity.

What happened after the paper

The source marks this deployed. That is a statement about the text, not a promise that every wallet or node has shipped it. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• What is covered by the signed bytes in Version bits with timeout and delay?
• Can the same signature be replayed on another chain, account, or message?
• Which primitive does the text require: Version bits with timeout and delay?

Terms

BIP 9

The public text titled Version bits with timeout and delay.

Deployed

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

The problem the paper names

A signature that does not commit to what the user saw can be replayed into a different spend, a different chain, or a different message.

What the design proposes

• This document specifies a proposed change to the semantics of the 'version' field in Bitcoin blocks, allowing multiple backward-compatible changes (further called "soft forks") to be deployed in parallel.
• It relies on interpreting the version field as a bit vector, where each bit can be used to track an independent change.
• Once the consensus change succeeds or times out, there is a "fallow" pause after which the bit can be reused for later changes.

How the mechanism is specified

• Taken from the specification, the next constraint is: It relies on interpreting the version field as a bit vector, where each bit can be used to track an independent change.
• Locate Version bits with timeout and delay in BIP 9 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

• A signature scheme is not a privacy system. It hides the signer only if the protocol says so.
• Wallet support is not the same as consensus validity.
• The source marks this deployed. That is a statement about the text, not a promise that every wallet or node has shipped it.

Why a venture studio still reads it

Use BIP 9 when a pitch says 'Version bits with timeout and delay' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.