Drivechain is a proposed design for connecting Bitcoin to sidechains with their own rules. It is commonly associated with two consensus proposals, BIP 300 (Hashrate Escrows) and BIP 301 (Blind Merged Mining). A sidechain is separate from the Bitcoin base chain, so Drivechain would require Bitcoin consensus changes to support the proposed peg. As of 2026-10-20, both BIPs are still marked Draft in the Bitcoin Improvement Proposals repository; they are not active rules on Bitcoin mainnet.
What the two proposals do
The proposals address different parts of a sidechain design. BIP 300 describes a proposed way to account for BTC moving into and out of a sidechain. BIP 301 describes how sidechain block producers could bid for Bitcoin miners to include commitments to their sidechain blocks. Neither proposal makes a sidechain identical to Bitcoin or automatically gives it Bitcoin’s full security.
BIP 300: Hashrate Escrows
BIP 300 specifies a proposed mainchain mechanism for sidechain deposits and withdrawals. The coins are tracked in a special Bitcoin output under the proposed rules; describing this simply as miners “custodying” user funds is misleading. The sidechain has its own software and ledger, while the mainchain would process deposits and approved withdrawal bundles.
- Deposit: a user sends BTC to the designated escrow output, and the sidechain recognizes the corresponding deposit under its own rules.
- Withdrawal request: a sidechain withdrawal is represented on Bitcoin as a bundle, rather than as an immediate one-to-one Bitcoin transaction for every sidechain action.
- Miner signalling: Bitcoin miners can acknowledge a proposed bundle through block data. In the BIP 300 draft, a bundle begins with 26,300 blocks remaining and needs 13,150 acknowledgements to succeed. At ten minutes per block, those figures correspond roughly to six months for the full timer and three months at the fastest possible acknowledgement rate; real block times vary.
Those are parameters in the draft specification, not behavior available on Bitcoin today. The long, public process is intended to make withdrawals slow and observable. It does not prove that miners could never approve a harmful withdrawal: whether hash-rate-based incentives are an adequate safeguard is one of the proposal’s central security debates.
BIP 301: Blind Merged Mining
BIP 301 describes a fee-bidding mechanism for sidechain block production. Sidechain users assemble a candidate sidechain block and bid on Bitcoin for the right to have that block committed. Under the proposal, Bitcoin miners could receive the bid without running the sidechain’s software themselves. That is why the proposal calls the mechanism “blind.”
This is not a promise that Bitcoin miners validate every sidechain transaction. A sidechain still has its own rules and participants; BIP 301 concerns how its block producer can pay Bitcoin miners. The proposed fees may give miners an additional incentive, but incentives are not the same thing as a security guarantee.
Security trade-offs and criticism
Supporters see Drivechain as a way to experiment with different features on separate chains while keeping Bitcoin’s base layer comparatively limited. Critics focus on the consequences of allowing miner signalling to authorize withdrawals from a sidechain escrow. If enough hash power cooperated on an invalid withdrawal, the result could put the sidechain’s backing at risk under the proposed rules.
The disagreement is not settled by saying miners are economically rational. A rationality argument is an assumption about incentives; it is not an automatic protocol veto or a guarantee against coordination, coercion, or changing market conditions. Sidechain consensus, peg-out rules, miner incentives, and the ability of users to detect and respond to problems all matter when assessing a particular implementation.
Bitcoin status and the eCash project
Drivechain’s proposal status must be separated from projects that implement or test similar software on another network. The Bitcoin BIPs repository lists both BIP 300 and BIP 301 as Draft. LayerTwo Labs and the eCash project describe eCash (ECX) as a separate Bitcoin-derived network intended to use Drivechain; that does not activate BIP 300 or BIP 301 on Bitcoin’s BTC network.
As of 2026-10-20, eCash’s own roadmap marks its Alpha and Beta milestones as complete and lists a separate eCash mainnet for around 31 October 2026 at Bitcoin block height approximately 973,728. That is the project’s published schedule, not a confirmed Bitcoin upgrade, and the site notes that block production makes the calendar estimate uncertain. This distinction is important when comparing a proposal, a test network, and a separate fork.
History
- 2017: BIP 300, titled “Hashrate Escrows,” was assigned in the Bitcoin BIPs repository.
- 2019: BIP 301, titled “Blind Merged Mining,” was assigned as a second draft specification.
- 2026: The eCash project announced a separate fork using Drivechain and published Alpha, Beta, and planned mainnet milestones. The Bitcoin repository still lists the two BIPs as Draft.
Common misconceptions
“Drivechain is already enabled on Bitcoin.”
No. BIP 300 and BIP 301 remain Draft in the Bitcoin BIPs repository. Software or test networks associated with a separate fork do not change Bitcoin mainnet consensus.
“Bitcoin miners directly hold every user’s sidechain coins.”
That phrasing oversimplifies the proposed design. BIP 300 specifies a special mainchain output and a withdrawal-bundle process governed by proposed consensus rules; it is not an ordinary company custody account.
“Blind merged mining means Bitcoin miners validate the sidechain.”
BIP 301 is about bids and block commitments. Sidechains keep separate rules and validation; the proposal does not make Bitcoin miners responsible for checking every sidechain transaction.
Social Media Sentiment
- Reddit (r/btc): In one small discussion on 16 October 2026 about the proposed eCash fork, commenters identified BIP 300/301 activation as a central goal, while others criticized the fork’s design and raised naming and governance concerns. This is a snapshot of one thread, not a representative measure of Bitcoin users or evidence about the proposal’s technical safety. Read the r/btc discussion.
Last updated: 2026-10
Related Terms
See Also
- Are Layer 2 Networks Actually Decentralized?
- How Do Crypto Bridges Work — And Why Are They Such a Hack Target?
- What Are Zero-Knowledge Proofs?
- Swap crypto with ChangeNOW
Sources
- BIP 300: Hashrate Escrows (draft specification) — The Bitcoin BIPs repository gives the proposal’s status, deposit and withdrawal design, acknowledgement thresholds, and block-count parameters.
- BIP 301: Blind Merged Mining (draft specification) — The primary specification describes the sidechain block-bidding process and what miners would and would not need to run.
- eCash: Drivechains, BIP 300 and BIP 301 — The project explains its own implementation and explicitly distinguishes its separate network from Bitcoin’s BTC network.
- eCash: What to Expect — The project roadmap states its planned network milestones and fork-height estimate; it is evidence of the project’s plan, not an independent confirmation of a Bitcoin upgrade.