getblocktemplate - Pooled Mining

The five-minute read

One action, walked through

1. Open BIP 23 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: Extensions to the getblocktemplate JSON-RPC call to enhance pooled mining.
3. Name the object that changes: JSON, RPC.
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 23 at the status the text itself states: Deployed.
• The object that has to change is JSON, RPC. 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 - Pooled Mining accept, and what may it ignore?
• Is this consensus, peer policy, or an application interface?
• Which names does the text pin down: JSON, RPC?

Terms

BIP 23

The public text titled getblocktemplate - Pooled Mining.

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

• Extensions to the getblocktemplate JSON-RPC call to enhance pooled mining.
• There is reasonable concerns about mining currently being too centralized on pools, and the amount of control these pools hold.
• By exposing the details of the block proposals to the miners, they are enabled to audit and possibly modify the block before hashing it.

How the mechanism is specified

• Taken from the specification, the next constraint is: There is reasonable concerns about mining currently being too centralized on pools, and the amount of control these pools hold.
• Locate JSON, RPC in BIP 23 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 23 when a pitch says 'getblocktemplate - Pooled Mining' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.