Hashrate Escrows (Consensus layer)
Drivechain hashrate escrows: miners vote over months on sidechain withdrawals. Draft; never activated on Bitcoin.
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 explorerDrama
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
In the Bitcoin Takeover Wiki
- Drivechains (BIP-300/301) Concepts
- eCash (ECX) Forks
- Paul Sztorc People
Heard on Bitcoin Takeover
- S9 E4: Paul Sztorc on the Philosophy of BIP 300 & Prediction Markets▶ listen
- S14 E10: Paul Sztorc on Drivechains & Attacking Bitcoin▶ listen
- S15 E68: Paul Sztorc on Activating Drivechains via CUSF (Core Untouched Soft Fork)▶ listen
- S17 E21: Paul Sztorc on activating drivechains on eCash▶ listen at 3:10timestamp transcript-derived, pending a listen
- S17 E37: Vlad on why he backs the drivechain fork (solo outro)▶ listen at 23:54timestamp transcript-derived, pending a listen
- S14 E13: Paul Sztorc Reacts to Drivechains Reactions▶ listen
- S15 E16: Paul Sztorc Talks Bitcoin Scaling, But Can't Say Drivechains▶ listen