Bitcoin governance research, consensus engineering, and blockspace policy.
Five merge keys gate the repository, and the deployment layer can only refuse what they offer. The shortfall is legibility and credible commitment.
A line count of Bitcoin Core 32.1. The consensus rules are 10,122 code lines, 7% of the implementation. Wallet commits rarely also touch validation. The release exposes 171 RPC methods, 36 P2P message types, and 5 deployment slots.
ETF filings disclose a loose community of core developers. The public record shows five merge keys, no written review minimum, and no tested exit from the Core lineage.
Why Bitcoin cannot be governed like an open source project. A dictator is a good way to ship a kernel. It is a bad way to write Bitcoin's node software.
What has to happen, and in what order: why miner signaling fails without economic nodes, why the spec track and the pool track have to run together, and what floor, mid, and ceiling look like through the 2028 halving.
A defense of toxic maximalism: collaborative capture and uncontested Taproot, retail warnings that got discounted, irreversible bugs, and why fraud-calling stays while internal fights need a spec and an unbundled stack.
A research report on the structural failures of altcoins as monetary assets: security, decentralization, founder risk, and the smart contract rebuttal.
Coldcard's RNG defect, credentialed endorsement without seed-path audit, and the same verification gap in Bitcoin Core.
Bitcoin is a distributed consensus state transition ledger. Every node maintains an identical copy not because storing data is valuable, but because reaching...
What it costs to run a Bitcoin full node in 2026: hardware, bandwidth, power, learning, maintenance, and capital, plus network aggregates and the non-monetary data burden (v2.4).
Verification methodology as a governance question: Orange Paper, Specification Lock, and readable mathematical notation.
The Bitcoin spam debate blurs two layers. Consensus forces every validating node to accept whatever is in a valid block, monkey jpegs included. Relay and sto...
Why Dandelion, UTXO commitments, Erlay, and a formal spec sit unmerged, and what shipping them looks like.
A reference document for analytical reasoning about Bitcoin governance
Numbered arguments for debate and analysis. Narrative evidence, funding maps, and primary sources are in Who Controls Bitcoin; structural logic in The Social...
This document addresses the structural logic underneath Bitcoin's governance problem. The evidentiary case, the funding maps, the personnel history, and the ...
Every government in history has faced the same structural temptation. Spending buys loyalty, wages wars, builds empires, and wins elections. Taxation is unpo...
Eight common defenses of Core's implementation monopoly and why they fail logical scrutiny.
Bitcoin is not captured. The implementation that writes the defaults is capturable. Block size war, CVE-2018-17144, and the case for implementation diversity.
Bitcoin solved block consensus. Node software is still written by informal agreement.
1. What this document is 2. Generational 3. Geographic and Economic