getblocktemplate Updates for Segregated Witness

The five-minute read

One action, walked through

1. Open BIP 145 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: Modifications to the getblocktemplate JSON-RPC call ([[bip-0022.mediawiki|BIP 22]]) to support segregated witness as defined by [[bip-0141.mediawiki|BIP 141]].
3. Name the object that changes: JSON, RPC, GBT.
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 145 at the status the text itself states: Deployed.
• The object that has to change is JSON, RPC, GBT. 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 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 must an implementation of getblocktemplate Updates for Segregated Witness accept, and what may it ignore?
• Is this consensus, peer policy, or an application interface?
• Which names does the text pin down: JSON, RPC, GBT?

Terms

BIP 145

The public text titled getblocktemplate Updates for Segregated Witness.

Deployed

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

• Modifications to the getblocktemplate JSON-RPC call ([[bip-0022.mediawiki|BIP 22]]) to support segregated witness as defined by [[bip-0141.mediawiki|BIP 141]].
• Segregated witness substantially changes the structure of blocks, so the previous getblocktemplate specification is no longer sufficient.
• It additionally also adds a new way of counting resource limits, and so GBT must be extended to convey this information correctly as well.

How the mechanism is specified

• Taken from the specification, the next constraint is: Segregated witness substantially changes the structure of blocks, so the previous getblocktemplate specification is no longer sufficient.
• Locate JSON, RPC, GBT in BIP 145 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 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 145 when a pitch says 'getblocktemplate Updates for Segregated Witness' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.