Drivechain

Drivechain asks one question: if miners already secure bitcoin, can they also secure the vault holding a sidechain's deposits? The design gives them a vote, and a withdrawal needs 13,150 miner acknowledgements, roughly three months of blocks, before it pays out. Nothing about it is live, so anything selling you drivechain exposure is selling something else.

How it works

Status: BIP300 and BIP301 are Draft, authored by Paul Sztorc and CryptAxe. Neither has been activated on bitcoin mainnet, and there is no scheduled activation. The current way to run a bitcoin sidechain is a federated peg.

BIP300 calls its mechanism a hashrate escrow, and the name describes the security model exactly.

A sidechain occupies a numbered slot created by miner support, which accumulates over a window of 2,016 blocks and needs roughly half the hashrate behind it. Coins deposited to that sidechain go to a special output that no ordinary transaction can spend. The only thing that can move them is a withdrawal bundle: a single batch paying out up to 6,000 recipients at once, proposed publicly and then voted on.

Voting is deliberately glacial. Miners may add at most one acknowledgement per block, the bundle starts with 26,300 blocks on its clock, and it succeeds once it collects 13,150 acknowledgements. If the shortfall ever exceeds the blocks remaining, the bundle is thrown out early. Three months of public scrutiny for the fastest possible withdrawal is not an accident; it is the whole defense, on the theory that a theft attempt would be visible for a quarter of a year before it settled, giving everyone time to react.

BIP301 handles the other side of the arrangement. Blind merged mining lets a bitcoin miner earn a sidechain's transaction fees while committing to a sidechain block whose contents it never validates, so miners are not forced to run every sidechain's software to profit from it.

Where you see it

You see drivechain in mailing list arguments, test networks and conference talks, and nowhere in a wallet you can download and use with real coins.

The argument against it is straightforward: it hands miners a new job and a new revenue stream, and a majority of hashrate could vote through a bundle that steals a sidechain's deposits. The argument for it is that the same majority can already reorganize bitcoin, that the theft would be public for months, and that the alternative in practice is trusting a named federation instead. Both sides are describing real risks, and the disagreement is about which one is worse.

The practical warning is the one that matters most here. Because drivechain is permanently near activation and never activated, it attracts promotion, including chains that ship it by splitting away from bitcoin and promising holders free coins. Any offer that requires you to move coins, connect a wallet or type a seed phrase to claim something drivechain-related is a theft attempt. Nothing about a genuine consensus change ever asks for your seed.

Drivechain vs Liquid Network

Drivechain and Liquid are two answers to the same problem, and only one of them exists. Liquid's peg is 11 of 15 named companies with hardware modules, which is a group you can identify, regulate and sue, and which processes withdrawals in minutes. A drivechain peg would be anonymous hashrate voting over three months, which nobody can sue and nobody can rush. Liquid's failure mode is collusion or legal compulsion among known firms; drivechain's would be a mining majority approving a fraudulent bundle in plain sight and daring the network to respond.