A finite monetary supply for Bitcoin

The five-minute read

One action, walked through

1. Open BIP 42 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: Although it is widely believed that Satoshi was an inflation-hating goldbug he never said this, and in fact programmed Bitcoin's money supply to grow indefinitely, forever.
3. Name the object that changes: A finite monetary supply for Bitcoin.
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 42 at the status the text itself states: Deployed.
• The object that has to change is A finite monetary supply for Bitcoin. A neighbouring document with a similar name is not this one.
• Activation is a separate mechanism from the opcode or the sighash. This page does not pick a height.

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

• Which bytes become invalid under A finite monetary supply for Bitcoin, and which old transactions stay valid?
• Is enforcement in consensus, or only in the mempool policy of one client?
• Which of these objects does the text actually define: A finite monetary supply for Bitcoin?

Terms

BIP 42

The public text titled A finite monetary supply for Bitcoin.

Deployed

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

The problem the paper names

Bitcoin script and block validity only change when a soft fork says an old pattern is now invalid. Without that rule, every node is free to accept what this document wants to reject.

What the design proposes

• Although it is widely believed that Satoshi was an inflation-hating goldbug he never said this, and in fact programmed Bitcoin's money supply to grow indefinitely, forever.
• He modeled the monetary supply as 4 gold mines being discovered per mibillennium (1024 years), with equal intervals between them, each one being depleted over the course of 140 years.
• Prominent among them is the discussion on what to call 1 billion bitcoin, which symbol color to use for it, and when wallet clients should switch to it by default.

How the mechanism is specified

• Taken from the specification, the next constraint is: He modeled the monetary supply as 4 gold mines being discovered per mibillennium (1024 years), with equal intervals between them, each one being depleted over the course of 140 years.
• Locate A finite monetary supply for Bitcoin in BIP 42 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 soft fork does not bind a node that never upgrades. It binds the nodes that enforce the new rejection.
• Activation is a separate mechanism from the opcode or the sighash. This page does not pick a height.
• 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 42 when a pitch says 'A finite monetary supply for Bitcoin' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.