DRA

Drivechains AUTHOR TO HARDFORK BITCOIN I with PAUL SZTORC

April 24, 2026Original source

On April 24, 2026, Isabel Foxen Duke hosted Paul on Bitcoin Rails to discuss his planned eCash fork of Bitcoin, Drivechain activation through BIP300/301, CUSF, sidechains, merge mining, and miner incentives.

Highlights

Key Takeaways

eCash as a Direct Activation Path

Paul frames eCash as a Bitcoin code fork built to put Drivechain, BIP300/301, and CUSF into production while giving Bitcoin holders a parallel asset rather than asking them to abandon their BTC. The discussion presents the fork as a practical path for moving forward when soft fork activation has become socially difficult, while still keeping the original BIP300/301 soft fork route available. eCash is described as having a distinct name and identity, with the cash language emphasizing payments, wallet use, and everyday monetary function.

Drivechain's Miner-Governed Bridge

The conversation contrasts Drivechain with federated bridge models by emphasizing that BIP300 is designed around deposits and withdrawals governed through the mining process, not special signing keys or a standing multisig group. Paul explains sidechains as developer-created systems competing for activity, fees, and miner support, with Blind Merged Mining and miner incentives helping decide which sidechains remain economically active. That structure turns sidechains into a marketplace for new Bitcoin functionality, including privacy, scalability, prediction markets, and other applications that can run beside the base chain.

CUSF and Core Untouched Soft Forks

Paul describes CUSF, the Core Untouched Soft Fork, as a way to lower the coordination burden by leaving Bitcoin Core itself untouched while a separate client enforces additional rules. In that model, developers can experiment with op-Drivechain, op-cat, op-ctv, or other rule sets through an auxiliary layer that calls back into Bitcoin Core when blocks violate the added policy. The eCash plan uses this modular idea to activate Drivechain cleanly on the new chain, showing how BIP300/301 can be deployed without turning every protocol change into a direct Core editing process.