Timechain
Search Donate
Sponsors
Cake Wallet, private Bitcoin and Monero walletSideShift.ai, no-signup crypto exchangeOrangeRock, non-custodial bitcoin spot and perps tradingBraiins Hashpower, buy and sell Bitcoin hashrateLayer Two Labs, drivechains for Bitcoin
BIP 300

Hashrate Escrows (Consensus layer)

Draft Draft Consensus (soft fork) Specification Assigned 2017-08-14

Drivechain hashrate escrows: miners vote over months on sidechain withdrawals. Draft; never activated on Bitcoin.

Plain-English summary by Bitcoin Takeover, based on the BIP text.
From the BIP’s abstract

BIP-300 enables a new type of L2, where "withdrawals" (the L2-to-L1 txns) are governed by proof-of-work -- instead of a federation or fixed set of pubkeys. BIP-300 emphasizes slow, transparent, and auditable withdrawals that are easy for honest users to get right and hard for dishonest miners to abuse. The main design goal for BIP-300 is partitioning -- users can ignore BIP-300 txns if they wish; it makes no difference to L1 if the user validates all, some, or none of them. The second design goal is security -- users of the L2 should feel confident that, if the L2 network is paying a lot of fees, then miners will want to keep it around, and the withdrawals will therefore be processed…

Read BIP 300 on GitHubFind in explorer

Drama

Drivechains — A decade-long argument about whether Bitcoin should host sidechains at the consensus level, waged on podcasts as much as on mailing lists.

Authors

Paul Sztorc
Paul Sztorc2 BIPs · Wiki · X
CryptAxe2 BIPs

In the Bitcoin Takeover Wiki

0:000:00