Merged Mining allows the same search for a hash, the result of a mining calculation, to serve several compatible networks. A block is a group of transactions intended for addition to a network’s public history. Miners search for a calculation result that lets them submit that block for others to verify. Each network keeps its own history and rules. Sharing work therefore does not, by itself, mean sharing coins or having the same security.
Jan mines through a Mining Pool, a service coordinating miners’ work. One day he also sees a Namecoin reward on his dashboard. That need not mean his ASIC, a specialised mining machine, stopped working on Bitcoin for half the time. The pool can prepare a job so that the same search for a suitable hash serves both networks. If a result meets the relevant conditions, the work can also be proved to the auxiliary network. The machine has not doubled its computing power; its existing work has gained another use. The other network’s reward does not create extra bitcoins beyond Bitcoin’s rules. [1] [4]
We call Bitcoin the parent chain here and Namecoin the auxiliary chain. Auxiliary does not mean Bitcoin takes responsibility for it. A Bitcoin Full Node, a computer running software that independently checks the rules, validates Bitcoin transactions and blocks. It does not decide whether Namecoin transactions are valid too. Namecoin nodes must do that. Each network therefore maintains its own history and record of spendable coins. An application failure on the auxiliary network does not, by itself, invalidate a Bitcoin payment, and that network cannot use its rules to change Bitcoin’s. [1] [2]
A mining result is compared with a target: a numerical boundary the hash must not exceed. The hash is calculated from the header, which contains summary information about the proposed block. The miner varies some of that data and repeats the calculation until the resulting number is low enough. The auxiliary network may set an easier condition. Jan’s result can then qualify for its block without qualifying for a Bitcoin block. Rootstock explicitly distinguishes these outcomes: a result may qualify for both networks, only for Rootstock, or merely for the pool’s easier share condition, which provides ongoing evidence of work. A share alone is not a block on either network. Meeting the mining target does not excuse invalid transactions either: the block must also satisfy its network’s other rules. [3] [4]
The calculations need not all be repeated, but operations still require work. Someone must prepare auxiliary blocks, run their nodes, maintain software and submit proofs. A pool operator can handle this, so Jan’s ASIC need not run a node for every project itself. Payment is a separate question. Namecoin rewards are denominated in NMC, its own currency; whether the pool pays them to Jan, converts them or incorporates them into its offer differently depends on its terms. The amount actually received after deductions matters more than a colourful dashboard bonus. [1] [5]
That claim does not yet tell us how many miners actually participate. A smaller network does not automatically receive all of Bitcoin’s computing power. What matters is the work contributed, its concentration among operators and their incentives to maintain the network honestly. Namecoin also allows other parent chains using SHA-256d, meaning two applications of the same hash function. A quoted hashrate, the rate of calculation, therefore needs context. It cannot by itself establish equal resistance to rewriting recent history, or mean that the same number of confirmations offers the same assurance as on Bitcoin. Transaction confirmations count the block containing the transaction and the blocks added after it on that network. [1] [4]
When Jan sees an extra reward offer, he first needs to know which network and currency it involves and how he will actually receive it in his wallet. Users of the auxiliary network also need to know who validates its rules and what risks its software carries. Shared mining does not itself exchange one coin for another. If a project offers a bridge, a mechanism for moving value between networks, that bridge has its own conditions and risks. “Mined alongside Bitcoin” explains where part of the security comes from, not the whole product or the safety of money held in it. [1] [4]
Namecoin calls its proof AuxPoW, auxiliary Proof of Work. To prevent someone taking an arbitrary hash already found and attaching a different block afterwards, the auxiliary block must be cryptographically tied to the calculation beforehand. Its hash, a digital fingerprint, is linked through a Merkle Tree, a tree of hashes used to prove data inclusion, to data in the parent coinbase, the block’s special first transaction. Another branch proves that coinbase is included in the parent block header’s transaction commitment. Nodes check the full link, the data’s placement, tree size and an index also derived from the chain ID, the chain’s identifier. A borrowed hash without that link is insufficient. [2]
BIP 301 describes Blind Merged Mining (BMM). A BIP is a document proposing or describing rules and practices for Bitcoin; publishing it does not itself change the network’s rules. In this proposal, other participants assemble auxiliary blocks and offer Bitcoin miners a fee to include the corresponding commitment, a verifiable reference to the chosen block. Miners therefore need not choose its contents themselves. The proposal has its own rules requiring a change to consensus, the network’s shared validation rules; it is not a new name for deployed Namecoin AuxPoW. At this review, BIP 301 is listed as Draft in the official registry. Neither a BIP number nor an implementation alone proves activation on the Bitcoin network. [5]
For the clearest picture, read this entry together with Mining, Proof of Work, Bitcoin, Mining Pool, ASIC Miner, Full Node. The reverse links also lead from Sergio Demian Lerner.