Drivechain

Drivechain is a proposed mechanism, authored by Paul Sztorc as BIP-300 and BIP-301, that would let Bitcoin support sidechains with a miner-enforced two-way peg. The goal is to move BTC onto separate chains — for experimentation, scaling approaches, or features Bitcoin itself will never adopt — and back again, without a federation or trusted custodian holding the funds. As of this writing the proposal remains unactivated and is genuinely controversial within the development community; this entry presents it neutrally as a design worth understanding.

BIP-300: hashrate escrows

BIP-300 defines the peg. Coins moved to a sidechain are held on the main chain in a special output called a hashrate escrow. Getting coins back out is deliberately slow: a withdrawal is proposed as a bundle, and miners then vote on it block by block over a window spanning months. Only a withdrawal that accumulates sustained miner approval across that long period executes. The extended window is the security model — it gives the whole network time to scrutinize a proposed withdrawal, and makes theft require not a moment of malice but months of it, sustained publicly, by a majority of hashrate that would be visibly attacking a system it profits from. Custody thus rests on ongoing miner honesty rather than on a multisig of named parties.

BIP-301: blind merged mining

BIP-301 specifies how sidechain blocks get produced. Blind merged mining lets Bitcoin miners commit to a sidechain block in their coinbase without running that sidechain's node software — sidechain users assemble blocks and pay miners (in bitcoin) to include the commitment, and the miner earns the fee "blindly," never validating sidechain rules. This differs from classic merged mining, where the miner runs the auxiliary chain's node; blind merged mining keeps the marginal cost of supporting many sidechains near zero and avoids pressuring miners into ever-heavier validation duties.

The debate

Supporters argue Drivechain lets Bitcoin absorb innovation without base-layer risk: sidechains can try larger blocks, privacy features, or exotic contracts, users opt in with eyes open, and failures burn only those who chose the experiment. Critics counter that hashrate escrows hand miners a new custodial role and new temptations — a large enough escrow becomes a bounty that tests the very honesty assumption securing it — and that fee flows from sidechains could distort mining incentives on the main chain. Both camps make serious arguments, which is precisely why the proposal has sat unactivated for years while discussion continues.

Where it stands

Nothing about Drivechain is live on Bitcoin today; activation would require a soft fork with broad consensus that has not materialized. For contrast, Rootstock operates now as a federated sidechain using classic merged mining, illustrating the custody trade-off Drivechain aims to eliminate. For miners and node runners, Drivechain is worth following because it sits exactly on the fault line this site cares about: how much power the network can safely delegate to hashrate, and whether decentralization is better served by keeping Bitcoin minimal or by giving experimentation a sanctioned place to live.

The proposal has also produced working code, not just debate: implementations and test networks have existed for years, letting the mechanism be exercised even while activation remains out of reach. That matters for evaluating it honestly — the open questions about Drivechain are not whether the engineering functions, but whether the incentive assumptions hold at scale, and that is a question no testnet can settle. It is a useful case study in how conservatively Bitcoin changes: a fully specified, implemented proposal can wait indefinitely for consensus, and most Bitcoiners would call that patience a feature of the system rather than a failure of it.