A Security Disclosure Lands: How to Tell Severity From Noise
Vulnerability headlines rarely distinguish between a flaw in the protocol, in one implementation, in a wallet, or in a service. The four have…
NEWS
Industry News
A Fork Proposal Appears: How Bitcoin Actually Changes
Protocol change stories are usually written as politics. The mechanics are stricter than the coverage suggests, and most proposals never activate.
Reasoned analysis, not financial advice.
Bitcoin is volatile and you can lose money. Nothing here is a recommendation to buy or sell. Do your own research.
The short answer
Anyone can publish a proposal. Changing Bitcoin requires near-unanimous adoption by economically significant nodes, because a rule change that users do not run simply creates a different network that most people ignore.
A proposal is published and described as a plan to change Bitcoin. Publishing costs nothing. Activation is extremely hard, and the distance between the two is where most coverage goes wrong.
Soft and hard are not degrees of the same thing
A soft fork tightens the rules: blocks valid under the new rules remain valid under the old, so nodes that never upgrade continue to follow the chain. A hard fork loosens or alters them, so non-upgrading nodes reject the new blocks and the network splits. The first is a change users can decline to notice; the second forces everyone to choose.
Who actually decides
Not developers, who can only propose and write code. Not miners alone, who order transactions but cannot make nodes accept invalid blocks. The binding constraint is economic nodes — exchanges, custodians, payment processors, businesses and individuals running the software that defines which chain their money is on. A change those parties do not run is not an upgrade; it is a new asset with a similar name.
Why the process is slow by design
Bitcoin’s properties depend on rules being hard to alter. Slowness is the feature: a monetary system whose supply schedule could be changed by a motivated group would not offer the guarantee that makes it interesting. Proposals that fail to activate are the system working, not gridlock.
What to check in any fork story
Is it soft or hard? Has it been implemented, or only described? What activation mechanism is proposed, and what threshold? And who has publicly said they will run it — not “supports it”, but will run the code. That last question separates almost all serious proposals from almost all noise.
Key takeaways
- A soft fork tightens rules and non-upgraders keep following. A hard fork splits the network.
- Economic nodes decide, not developers and not miners alone.
- Slowness is the feature. Rules that were easy to change would not be worth much.
- Ask who will actually run the code, not who says they support it.
Related reading
A Fee Spike Hits the Mempool: What Actually Drives It
Fee spikes are reported as congestion or as distress. They are an auction for a fixed quantity of block space, and the bidders are not always who the…
A Custodian Announces an Audit: What Assurance It Actually Provides
Attestation, examination and audit are different engagements with different levels of assurance. The word used in the press release is often the…
Get The Signal
The week’s Bitcoin news, one reasoned take, and the on-chain number that mattered. Free, weekly.
Signal, not noise. Unsubscribe any time.