Drivechains have merit. Sztorc's Satoshi coin gamble ensures nobody will notice.

Drivechain is a mechanism design problem that Paul Sztorc has been working on for close to a decade. The core of BIP 300 is a "hashrate escrow": when someone wants to move funds from a Bitcoin sidechain back to mainchain, miners vote over a roughly three-month window. If miners don't actively block the withdrawal, it goes through. The bet is that economic incentives align miners with honest behavior, because censoring valid withdrawals destroys the value of the sidechains they're also mining.

The problem Drivechains solve is real. Bitcoin can't add new features without changing the base layer, and every base-layer change is a years-long political negotiation. Drivechains offer a "let a thousand sidechains bloom" answer: privacy sidechains, smart contract execution, high-throughput payments, all settling to Bitcoin. That case is sound. What Sztorc attached to it is not.

The mechanics matter here. A sidechain withdrawal creates a "WT^" hash that gets bundled into Bitcoin's coinbase. Miners signal support for that hash over roughly 13,150 blocks. If a threshold of miners don't block it, it clears.

This is structurally different from Bitcoin's current security model, where miners can't selectively deny valid transactions without the network noticing. Critics aren't wrong that this introduces a new trust surface. Sztorc's counterargument is that the game theory holds because theft by miners would immediately crater the value of every sidechain they mine. Neither side is making a bad-faith argument.

That debate has been running since 2015. It deserves resolution. Instead, it's getting swamped.

On April 27, Sztorc proposed attaching Drivechains to a Bitcoin hard fork called eCash that includes a plan for what happens to the eCash equivalent of Satoshi Nakamoto's dormant coins. Satoshi's wallets have sat untouched for over a decade. In a straight 1:1 airdrop, whoever holds those private keys would receive equivalent eCash at the same ratio. The proposal instead redirects those coins.

Critics immediately called it theft. That word spread faster than any explanation of BIP 300 ever has.

The technical argument for Drivechains is now secondary to a property-rights argument about coins that may not have a living owner. From an engineering standpoint, this is a prioritization failure. The hardest part of shipping a consensus change to Bitcoin is convincing developers and node operators that the change doesn't violate Bitcoin's core properties. The Satoshi coin mechanic hands every skeptic a non-technical objection that requires no code knowledge to make.

At the contract level, the two features have no dependency. Drivechains work or don't work regardless of what happens to Satoshi's eCash equivalent. BIP 300 and BIP 301 are complete proposals. They could ship independently. You don't need a coin redistribution to test whether hashrate escrow works.

What this bundling guarantees is that any honest technical evaluation of the withdrawal mechanism now comes loaded with the optics of touching coins that are widely regarded as untouchable. Engineers who might review the sidechain security model in good faith will spend their review cycles on the redistribution instead. You can watch it happening in the discussion threads already.

Sztorc knows the code well enough to have built and rebuilt this proposal across years of developer review. That makes the bundling decision hard to explain as oversight. It reads as a deliberate choice: ship the whole package or nothing. The engineering case for Drivechains doesn't require that bet. The proposal, as written, takes it anyway.