Drivechain

What Is a Drivechain?

A drivechain is a type of Bitcoin sidechain where proof-of-work miners collectively act as escrow agents for the two-way peg between the Bitcoin mainchain and the sidechain. Proposed by Paul Sztorc in 2015 and formalized through BIP 300 (Hashrate Escrows) and BIP 301 (Blind Merged Mining), drivechains aim to let developers deploy entirely new blockchains that use BTC as their native currency without requiring a trusted federation.

The core idea is straightforward: instead of trusting a group of known entities to custody sidechain funds (as Liquid Network does with its federation), drivechains trust Bitcoin's existing mining infrastructure. Miners vote over a long period (approximately six months) to approve or reject withdrawals from sidechains back to the Bitcoin mainchain. This slow withdrawal mechanism is designed to make theft detectable and give users time to respond.

The system supports up to 256 sidechains simultaneously, each identified by a single-byte ID. Activation would require a soft fork to Bitcoin's consensus rules, redefining the unused opcode OP_NOP5 as OP_DRIVECHAIN.

How It Works

Drivechain relies on two complementary proposals that handle different aspects of sidechain operation: BIP 300 manages the flow of BTC between layers, while BIP 301 handles sidechain block production.

BIP 300: Hashrate Escrow

BIP 300 defines six message types (M1 through M6) that miners embed in coinbase transactions using OP_RETURN outputs. These messages govern the full lifecycle of sidechain management:

• M1 and M2 handle proposing and acknowledging new sidechains
• M3 and M4 handle proposing and voting on withdrawal bundles
• M5 handles deposits from the mainchain to a sidechain (peg-in)
• M6 handles withdrawals from a sidechain to the mainchain (peg-out)

For deposits, users send BTC to a special OP_DRIVECHAIN output associated with a sidechain ID. The sidechain software detects this deposit and credits the user on the sidechain. This direction is relatively simple and does not require miner voting.

Withdrawals are where the hashrate escrow mechanism comes into play. Sidechain users batch their withdrawal requests into a single "withdrawal bundle" containing up to 6,000 individual outputs. A miner then proposes this bundle by including its blinded hash in an M3 coinbase message.

The Withdrawal Voting Process

Once a withdrawal bundle is proposed, a 26,300-block voting window begins (approximately six months at Bitcoin's ~10-minute block time). Each block, miners cast one of three votes:

1. ACK: approve the bundle, incrementing its score by 1
2. Abstain (0xFF): the score decreases by 1 as the remaining block count drops
3. Alarm (0xFE): an explicit signal that something may be wrong

The bundle's ACK score can change by at most +1 or -1 per block. If the score reaches 13,150 (roughly 50% of the voting window), the withdrawal succeeds and the corresponding M6 transaction can be included on-chain. If the "blocks remaining" counter hits zero before reaching the threshold, the bundle is discarded and users must try again.

This slow, public voting process is intentional. Any attempted theft would be visible for months, giving the community time to coordinate a response. Only one withdrawal bundle can succeed per sidechain at a time.

BIP 301: Blind Merged Mining

Traditional merged mining requires miners to run full node software for every chain they want to mine. BIP 301 eliminates this requirement through blind merged mining (BMM), where miners secure sidechains without reading or validating sidechain data.

The protocol involves two participants:

• A sidechain node operator ("Simon") who assembles sidechain blocks, selects transactions, and collects sidechain fees
• A Bitcoin miner ("Mary") who performs all hashing work and receives payment in BTC for including a commitment to Simon's block

Simon broadcasts a BMM Request transaction that pays a fee to the miner and contains a commitment (h*) to his proposed sidechain block. Mary selects the highest-paying request and includes the matching h* in her coinbase output as a BMM Accept. Both must appear in the same mainchain block. Simon collects sidechain transaction fees; Mary collects Simon's BTC payment. The miner never needs to understand or validate the sidechain.

# BMM Request (broadcast by sidechain operator)
OP_RETURN 0x00bf00 <sidechain_id> <h*> <prev_main_block_hash>

# BMM Accept (in miner's coinbase)
OP_RETURN 0xD1617368 <sidechain_id> <h*>

Drivechain vs. Federated Sidechains

The most direct comparison for drivechains is the Liquid Network, a federated sidechain operated by Blockstream. The two approaches represent fundamentally different trust models for securing sidechain funds:

Drivechain proponents argue that most users would not actually wait months for withdrawals. Instead, they would use atomic swaps or HTLCs with specialized parties (exchanges or market makers) for near-instant settlement, similar to how Lightning users rarely wait for channel close timeouts.

Proposed Sidechains

Several sidechains have been demonstrated on the Drivenet testnet (a modified Bitcoin Core with BIP 300 activated):

• zSide: a privacy-focused sidechain using Zcash's zk-SNARKs for confidential transactions with BTC
• EthSide: an EVM-compatible sidechain allowing Solidity smart contracts to run with BTC as the native currency
• Thunder: a large-block sidechain designed for high-throughput scaling
• BitNames: a Namecoin-inspired sidechain for decentralized domain name registration

The permissionless nature of drivechains means any developer could deploy new sidechains without needing approval. Proponents argue this would allow Bitcoin to absorb use cases currently served by altcoins (privacy, smart contracts, high throughput) while keeping the base layer conservative.

Why It Matters

Drivechain sits at the intersection of two critical Bitcoin debates: how to scale beyond the base layer, and how to add new functionality without modifying Bitcoin Script itself.

The block subsidy decreases with each halving, and Bitcoin's long-term security budget depends on transaction fees replacing the subsidy. Drivechain proponents argue that sidechain fees paid to miners via blind merged mining could provide a significant new revenue stream, strengthening Bitcoin's security in a post-subsidy future.

The proposal also represents a different philosophy from other Layer 2 approaches. Where Lightning Network optimizes for fast, small payments and protocols like Spark use statechains for off-chain ownership transfer, drivechains aim to enable entirely new blockchain designs that inherit Bitcoin's proof-of-work security. For a broader comparison of these approaches, see the Bitcoin Layer 2 comparison.

Risks and Considerations

Miner Custodial Authority

The most fundamental criticism of drivechains is that they give miners the ability to steal sidechain funds. In standard Bitcoin transactions, no amount of hashrate can forge a digital signature: cryptographic security is absolute. Drivechains break this property by allowing a sustained 51% hashrate majority to approve fraudulent withdrawals over the voting window.

Proponents counter that the ~6-month withdrawal period makes theft slow, visible, and deterrable through user-activated soft forks. Critics argue that designing a system that requires the threat of contentious soft forks as a security mechanism is itself a risk.

Mining Centralization Pressure

Reviewing and voting on withdrawal bundles across multiple sidechains adds operational complexity for miners. Larger mining pools can absorb this overhead more easily than solo miners, potentially pushing toward greater centralization. The BMM market also favors well-capitalized sidechain operators who can afford to bid for block production rights.

MEV and Vertical Integration

Drivechains introduce miner extractable value dynamics to Bitcoin. Miners who also operate sidechain nodes could extract additional value by reordering sidechain transactions, creating incentives for vertical integration between mining and sidechain operation that do not exist today.

Activation Uncertainty

After years of debate, drivechains have not achieved sufficient community consensus or miner signaling for activation as a Bitcoin soft fork. BIP-110 signaling in mid-2026 showed support well below the 55% threshold required for activation. The proposal's creator, Paul Sztorc, announced an alternative path through eCash, a hard fork of Bitcoin that would activate BIP 300 and BIP 301 on a separate chain, though this approach has drawn its own controversy.

Slow Withdrawal Trade-off

The ~6-month withdrawal window is both the primary security feature and the primary usability cost. While atomic swaps and market makers can provide faster exits, these introduce their own counterparty risks and liquidity requirements. During periods of sidechain instability, exit liquidity could dry up precisely when users need it most.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.