DRA

The Problem with Bitcoin Governance | PAUL SZTORC

August 27, 2025Original source

On August 27, 2025, Paul joined Isabel Foxen Duke to trace Drivechain’s origins, BIP300/301, sidechains, Bitcoin governance, soft forks, CUSF, Lightning, merge mining, and the case for miner-aligned Layer 2 scaling.

Highlights

Key Takeaways

Drivechain as Governance Outlet

Paul frames Drivechain as a practical answer to recurring Bitcoin governance disputes: move persistent disagreements into opt-in sidechains while preserving a conservative base layer. BIP300/301 lets different scaling, privacy, and application designs compete without requiring every user to adopt each feature. The conversation connects this to the block size era, where the desire for larger blocks and more experimentation could have been routed through sidechains instead of dividing attention across separate coins.

From Truthcoin to BIP300/301

Paul describes how his work on prediction markets and Truthcoin led into the sidechain problem. The 2014 pegged sidechains discussion showed that Bitcoin could host more specialized systems, but Paul wanted a simple two-way peg that treated Bitcoin as the clear base chain. Drivechain emerged as that asymmetric Layer 2 design, with BIP300 handling withdrawals and BIP301 enabling Blind Merged Mining, so sidechains can add functionality while remaining anchored to Bitcoin.

CUSF and Miner-Aligned Scaling

The later part of the conversation focuses on implementation strategy and incentives. Paul explains the move toward CUSF, or Core Untouched Soft Fork, as a way for BIP300/301 activation to avoid dependence on Bitcoin Core code changes. He also emphasizes that successful Layer 2 systems should pay miners through merge mining, because that keeps users, block producers, and Bitcoin’s security budget economically aligned. Blind Merged Mining lets specialized sidechain block builders operate without burdening Layer 1 miners.