Drivechain is a Bitcoin sidechain proposal that would let BTC-backed balances be used on separate blockchains with their own transaction rules. It is commonly associated with BIP 300, which specifies hashrate escrow, and BIP 301, which describes blind merge mining. Its aim is to support experimentation and additional transaction capacity outside Bitcoin’s mainchain, while keeping individual sidechain rules outside mainchain validation.
BIP 300 is marked Draft in its specification. Publishing a BIP or running a test implementation does not, by itself, establish that these mechanisms are active on Bitcoin mainnet.
How the Two-Way Peg Works
In the proposed Drivechain two-way peg, a deposit locks BTC in an escrow output on Bitcoin’s mainchain. The sidechain recognizes that deposit and makes a corresponding balance usable under its own rules. Coins do not literally travel between blockchains; the sidechain records balances backed by the escrowed BTC.
To return funds to the mainchain, individual withdrawal requests are combined into a withdrawal bundle. Successful authorization allows escrowed BTC to be released to the specified mainchain recipients. This differs from an ordinary Bitcoin payment because access to the funds depends on the peg’s withdrawal-approval mechanism.
Hashrate Escrow and Withdrawals
Hashrate escrow is the BIP 300 mechanism for miner-controlled withdrawal authorization. It escrows bitcoin, not computing power, and does not reserve a portion of Bitcoin’s mining capacity. Miners vote on proposed withdrawal bundles over an extended period, and a bundle must meet the specified approval conditions before escrowed BTC can be released.
Under Drivechain, Bitcoin nodes enforcing the proposed rules check the voting and withdrawal conditions rather than validating the sidechain’s transaction history. The voting result therefore authorizes a payout without proving that it matches legitimate sidechain balances. A withdrawal that satisfies the mainchain mechanism can still be improper from a sidechain user’s perspective.
Looking for liquidity, exploring on-ramp/off-ramp services, or seeking expert guidance?
Get startedBlind Merge Mining
Blind merge mining, described in BIP 301, concerns sidechain block production rather than permission to withdraw escrowed funds. Bitcoin miners can receive fees for including commitments to sidechain blocks in their Bitcoin blocks without needing to validate all sidechain transactions. This connects sidechain block production to Bitcoin mining; it is not merely a signal of support for a sidechain.
Sidechain participants still need to validate blocks and enforce that chain’s transaction rules. Drivechain’s mining and peg mechanisms serve different purposes: one compensates miners for block commitments, while the other governs the release of BTC from escrow. Neither mechanism makes Bitcoin nodes validators of the sidechain’s full history.
Capabilities and Withdrawal Risks
Drivechain would allow sidechains to experiment with transaction formats or features that Bitcoin’s mainchain does not support. Additional capacity, lower fees or different privacy properties are possibilities, not automatic benefits; outcomes depend on each sidechain’s design, usage and adoption. The proposal would require Bitcoin consensus changes through a soft fork. Backward compatibility does not mean that no base-layer changes or upgrade risks exist.
The central security tradeoff is dependence on miner behavior when funds are withdrawn. Sufficiently coordinated miners could approve improper payouts or obstruct legitimate withdrawals. Expected fee income is intended to encourage miners to preserve a useful sidechain, but that incentive does not guarantee protection against theft or censorship. Sidechain balances therefore do not share the same security assumptions as BTC held directly on the mainchain. Users must consider both the sidechain’s own rules and the peg’s withdrawal conditions: fast sidechain transactions do not imply fast or unconditional access to mainchain BTC.