Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£867.69
EST. MONTHLY
203
DAYS
EST. ROI
This guide explains BIP 301 blind merged mining in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.
TL;DR
- What it is: BIP 301 is a Draft consensus soft-fork proposal for Blind Merged Mining. Sidechain users assemble sidechain blocks and bid on Bitcoin layer one; miners may accept one candidate per sidechain and collect its payment without running that sidechain’s node.
- Why it matters: BIP 301 proposes a specialised market between sidechain block producers and Bitcoin miners. Its Draft consensus status, one-winner rule and separation of validation duties must remain explicit.
- Current position: The design changes Bitcoin validation rules and is not active merely because implementations or enforcer software exist.
BIP 301 blind merged mining in simple English
BIP 301 blind merged mining: A sidechain user chooses transactions and a sidechain block hash, then offers layer-one fees. The Bitcoin miner selects a bid without validating the sidechain state.
Simple example
A node operator wants to understand BIP 301 blind merged mining. Model reorgs, stale previous-block commitments, duplicate requests, malformed OP_RETURN, miner censorship, fee competition and enforcer disagreement on isolated networks before any policy conclusion.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- Consensus:
- The shared rules full nodes use to decide whether blocks and transactions are valid.
- Soft fork:
- A proposed tightening of Bitcoin rules that old nodes may not enforce themselves.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Draft consensus status
The BIP labels itself Consensus (soft fork) and Draft. Do not describe it as deployed Bitcoin behaviour or enable production logic without an actual, verified activation process.
Blind division of labour
A sidechain user chooses transactions and a sidechain block hash, then offers layer-one fees. The Bitcoin miner selects a bid without validating the sidechain state.
BMM Accept
The miner places an OP_RETURN commitment in coinbase containing the defined header, one-byte sidechain number and 32-byte sidechain block hash. One choice identifies the endorsed candidate.
BMM Request
A bidder transaction commits to its header, sidechain number, candidate hash and previous mainchain block hash. Binding the previous block makes requests history-specific and short-lived.
One winner
Consensus permits only one matching Request per sidechain in a mainchain block and requires an Accept. Competing bidders expect most requests never to confirm.
Incentives and boundaries
Miners collect layer-one payments, while sidechain validation remains with sidechain users. Bitcoin validation cannot prove the sidechain block is economically correct.
Evaluation plan
Model reorgs, stale previous-block commitments, duplicate requests, malformed OP_RETURN, miner censorship, fee competition and enforcer disagreement on isolated networks before any policy conclusion. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness. Record source commit, binary hash, network, chain identity, configuration and dependencies.
Frequently asked questions
What is the main point of BIP 301 blind merged mining?
BIP 301 blind merged mining: A sidechain user chooses transactions and a sidechain block hash, then offers layer-one fees.
For BIP 301 blind merged mining, what should a beginner know about draft consensus status?
The BIP labels itself Consensus (soft fork) and Draft. Do not describe it as deployed Bitcoin behaviour or enable production logic without an actual, verified activation process.
For BIP 301 blind merged mining, what should a beginner know about blind division of labour?
A sidechain user chooses transactions and a sidechain block hash, then offers layer-one fees.
For BIP 301 blind merged mining, what should a beginner know about bmm Accept?
The miner places an OP_RETURN commitment in coinbase containing the defined header, one-byte sidechain number and 32-byte sidechain block hash.
Conclusion
BIP 301 proposes a specialised market between sidechain block producers and Bitcoin miners. Its Draft consensus status, one-winner rule and separation of validation duties must remain explicit.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.