Merged mining lets miners reuse the same proof-of-work computations across more than one compatible blockchain. In a typical AuxPoW setup, miners hash a parent-chain block header that commits to an auxiliary-chain candidate block. Each chain applies its own validation rules to determine whether the resulting work can support a valid block.

What Is an Auxiliary Chain in Merged Mining?

In merged mining, an auxiliary chain is a blockchain that accepts proof of work performed for another blockchain, known as the parent chain. The auxiliary chain does not receive a share of a miner's hashrate in the conventional sense of splitting hardware time between two workloads. Instead, it verifies cryptographic evidence that the parent-chain mining work also satisfies the auxiliary chain's own proof-of-work requirement. This verification mechanism is called Auxiliary Proof of Work, or AuxPoW.

“Auxiliary chain” describes a chain's role in merged mining. It does not, by itself, imply an asset peg or a two-way bridge to the parent chain. Terminology around “sidechains” varies: Namecoin's own documentation uses “merge-mined sidechain” and distinguishes it from a pegged sidechain. Namecoin and Dogecoin maintain their own consensus rules, transaction formats, and node software (Namecoin FAQ).

Parent Chain vs. Auxiliary Chain: The Key Difference

The parent chain is the network on which the actual proof-of-work hashing takes place. ASICs continue to hash the parent chain's block header exactly as they would if no auxiliary chain existed. The parent chain generally requires no awareness of the auxiliary chain and no changes to its own consensus rules.

The auxiliary chain is the network that opts into accepting parent-chain work as valid proof of work for its own blocks. It does this by defining consensus rules for verifying an AuxPoW proof: a package of data that links a candidate auxiliary block to a specific parent-chain block header. That header does not need to become an accepted block on the parent chain.

How AuxPoW Connects the Two Chains

A typical AuxPoW flow can be described in five steps.

1. The auxiliary-chain node or mining software constructs a candidate block using the target required by that chain's consensus rules.
2. The mining pool or software commits the auxiliary block header's hash into the parent chain's block template, typically inside the coinbase transaction. Where a pool merges multiple auxiliary chains at once, their block hashes can be organized into a Merkle tree so a single coinbase entry represents several auxiliary chains.
3. ASICs hash the parent-chain block header as a normal mining job. The auxiliary chain does not require a separate ASIC hashing workload.
4. The pool or mining software checks resulting proof-of-work hashes against the applicable targets and submits qualifying candidates. If the auxiliary chain's target is higher and therefore easier to satisfy, a hash can qualify for the auxiliary chain without qualifying for the parent chain.
5. The auxiliary-chain node validates the AuxPoW evidence and the auxiliary block's other consensus requirements. The evidence includes the parent block header, its coinbase transaction, a Merkle branch linking that transaction to the header's Merkle root, and the proof linking the auxiliary block header's hash to the coinbase commitment. When multiple auxiliary chains are represented, this includes an auxiliary-chain Merkle branch. In the Namecoin-style design, the chain identifier helps determine the auxiliary block hash's position in that tree; it does not replace the proof that the specific block was committed.

This structure lets the auxiliary chain verify the commitment and the work independently of whether the parent chain accepts the header as a block (Merged Mining Specification).

Target, Difficulty, and What “Valid” Means

A proof-of-work hash meets a chain's target when its numeric value is less than or equal to that target. A higher numeric target is easier to satisfy and corresponds to lower difficulty.

For a job where the auxiliary chain's target is higher than the parent chain's target, the same proof-of-work hash has three possible outcomes:

• It meets both targets.
• It meets only the auxiliary chain's target.
• It meets neither target.

Under that assumption, a hash cannot meet only the parent chain's target: any value low enough to meet the stricter parent-chain target also meets the easier auxiliary-chain target. This ordering is a condition of the example, not a requirement that auxiliary chains always have easier targets.

Meeting a target is only one part of block validity. A missing or invalid auxiliary commitment, an outdated auxiliary candidate, or a failure to satisfy other consensus rules can prevent the auxiliary block from being accepted even when the hash meets its target.

The historical Namecoin merged-mining specification includes an example of a parent-header hash that satisfied Namecoin's target without satisfying Bitcoin's. The auxiliary block could therefore be accepted without a corresponding accepted Bitcoin block (Merged Mining Specification).

Real-World Examples

Bitcoin and Namecoin

Namecoin was the first major deployment of AuxPoW and remains a clear reference implementation of the model: a parent block header, a coinbase commitment, Merkle proofs, and auxiliary-chain validation rules. Namecoin activated merged mining at block 19,200. This example is useful for illustrating the original protocol structure rather than current market activity (“Echoes of the Past,” Appendix A.1).

Litecoin and Dogecoin

Dogecoin activated AuxPoW support at block 371,337 on September 11, 2014, after which Dogecoin's own proof-of-work requirement could be satisfied using compatible Scrypt work also used for Litecoin (“Echoes of the Past,” Table 1). This pairing is a useful miner-facing illustration of merged mining because both chains use the same hashing algorithm and remain actively mined today.

In this arrangement, a Scrypt ASIC is not allocated half to Litecoin and half to Dogecoin; the pool constructs compatible work so that a single proof-of-work attempt can be recognized by both networks under their respective rules.

Bitcoin and Rootstock

Rootstock is another example of merged mining. Bitcoin miners can reuse their mining infrastructure and proof-of-work computations to participate in Rootstock mining, earning additional transaction fees. This illustrates how merged mining can support a separate blockchain without splitting the ASIC hashing workload (Rootstock Merged Mining Reference).

Does Merged Mining Split Hashrate?

No. A miner's hashrate is not divided between the parent chain and the auxiliary chain the way it might be divided between two unrelated coins in conventional switch mining. The ASIC performs one continuous hashing workload on the parent-chain block header. The pool builds the auxiliary commitment into that work, and each chain checks the resulting candidates under its own rules.

Block acceptance is not necessarily one-to-one across the chains. A hash may meet only the auxiliary chain's target, and a hash that meets both targets still needs valid, timely block candidates for both networks. The distinction is between sharing proof-of-work computations and obtaining accepted blocks.

How Mining Pools Handle Merged Mining and Rewards

For a pool miner, three layers should be kept distinct:

• Mining hardware submits shares to the pool based on the assigned job.
• The pool constructs the merged-mining job, including the auxiliary-chain commitment, tracks submitted shares, detects qualifying block candidates on either chain, and applies its payout rules.
• Auxiliary-chain consensus independently decides whether a submitted AuxPoW block is valid according to that chain's own rules.

Because of this separation, an individual miner may receive a reward tied to an auxiliary-chain block under the pool's payout policy even though that miner did not personally submit the winning share. This is standard pool accounting behavior and is not specific to merged mining. Auxiliary rewards therefore need not mirror a miner's own block discoveries or parent-chain block discovery on a one-to-one basis.

Before connecting hardware, check which parent and auxiliary chains the pool supports, which payout methods qualify for auxiliary rewards, and whether minimum balances or settlement timing rules apply. These are pool operating rules rather than underlying AuxPoW consensus rules, and they can change over time.

ViaBTC's LTC Merged Mining Coins Mining Tutorial explains supported LTC pairings, including DOGE, and their reward rules. Use the relevant coin's mining setup guide for connection details; ViaBTC's BTC Mining Guide, for example, provides BTC mining endpoints and worker setup instructions.

What Merged Mining Does—and Does Not—Mean for Security

Merged mining can allow an auxiliary chain to draw on parent-chain mining participation, but this does not make the auxiliary chain's security equivalent to the parent chain's. Relevant factors include the proportion of parent-chain miners or pools that actually enable the auxiliary commitment, whether miners can withhold or redirect auxiliary-chain work, the auxiliary chain's own difficulty adjustment and confirmation policy, and the incentives created by auxiliary-chain block rewards and fees.

Rootstock's documentation reports that more than 85% of Bitcoin hash power participates in securing Rootstock through merged mining, while also noting that the cost of a double-spend attack can remain lower than for Bitcoin. The percentage is a project-published claim with no calculation methodology or measurement window disclosed on that page, as checked on September 28, 2026. Readers should treat participation figures as one input among several, not as a standalone security guarantee (Rootstock Merged Mining Reference).

Merged mining also requires more than matching proof-of-work algorithms. The auxiliary chain must implement AuxPoW or a compatible design, and the pool must support the corresponding block-template construction, submission, and payout workflow for that specific pairing.

FAQ: Merged Mining and Auxiliary Chains

Is merged mining the same as dual mining?

No. Merged mining reuses a single proof-of-work attempt so that it can potentially be recognized by more than one compatible chain under each chain's own rules. Dual mining, by contrast, typically refers to running separate mining processes—often on different hardware resources or algorithms—rather than deriving validity for a second chain from the same hash.

Does the parent chain need to support the auxiliary chain?

Generally no. The auxiliary chain is the one that adds AuxPoW verification logic. The parent chain typically requires no special awareness of which auxiliary chains, if any, are using its coinbase commitments.

Can a miner mine an auxiliary chain without mining its parent chain?

It depends on the auxiliary chain's consensus rules and what “mining its parent chain” means. Some chains permit standalone mining; Namecoin's documentation describes mining NMC directly while recommending merged mining (How to Get Namecoins).

For an AuxPoW block, the miner must construct a valid AuxPoW proof using a parent-format block header. That does not mean the header must meet the parent chain's target or be submitted to and accepted by the parent network. Whether a chain also accepts ordinary proof-of-work blocks without AuxPoW is a separate, chain-specific rule.

Does merged mining guarantee extra profit?

No. Auxiliary-chain rewards depend on that chain's block reward, transaction fees, market price, difficulty, and the pool's specific payout rules and fee structure. Merged mining creates the technical possibility of earning an additional asset from the same hashing work, but actual returns vary and are not guaranteed.

References

• Merged Mining Specification, Bitcoin Wiki
• Namecoin FAQ
• How to Get Namecoins, Namecoin
• Rootstock: Merged Mining Reference, Rootstock Developer Documentation
• “Echoes of the Past: Recovering Blockchain Metrics From Merged Mining,” IACR ePrint 2018/1134
• ViaBTC: LTC Merged Mining Coins Mining Tutorial
• ViaBTC: BTC Mining Guide