Merged Mining and Solo Pool Mining Operate at Different Layers
Merged mining and solo pool mining are often discussed as if they were competing mining strategies, but they answer two unrelated questions. Merged mining is a protocol-level arrangement that determines whether a single proof of work can be recognized by more than one compatible blockchain. Solo pool mining is a reward-distribution arrangement that determines who receives a block reward once a valid block is found. A miner can evaluate these two features independently, and in principle a solo pool could support merged mining, provided the parent chain, the auxiliary chain, and the pool's current implementation all allow it (en.bitcoin.it).
This article separates the two concepts, explains how each works, and outlines what a miner should verify before connecting hash rate to either arrangement.
What Is Merged Mining?
In an AuxPoW (Auxiliary Proof-of-Work) setup, a miner builds a block for a parent chain—the chain on which hashing actually occurs. A compatible auxiliary chain can accept that same parent-chain proof of work if the submitted data proves two things: that the auxiliary block was committed to the parent block's coinbase transaction, and that the parent-chain hash also satisfies the auxiliary chain's own difficulty target. The parent chain does not need to validate or even be aware of the auxiliary chain's rules (en.bitcoin.it).
Bitcoin and Namecoin are the foundational example of this structure: Namecoin accepts Bitcoin's SHA-256 proof of work through AuxPoW without requiring any additional hashing from the miner. Outside the Bitcoin family, Litecoin and Dogecoin illustrate the same mechanism on Scrypt-based chains; Dogecoin Core's documented protocol features list AuxPoW as valid proof of work, with explicit validation logic in its source code. These examples make a key point concrete: merged-mining compatibility is protocol-specific. A miner cannot simply point hash rate at an arbitrary chain and expect AuxPoW to apply—the auxiliary chain must be built to recognize the parent chain's work, and the pool must implement the corresponding template and submission logic.
Merged mining does not increase a miner's physical hash rate, and it does not change the probability of finding a parent-chain block at a given hash rate. What it may add is eligibility for auxiliary-chain rewards from the same submitted work, subject to the pool's support for that auxiliary chain and its distribution rules.
What Is a Solo Mining Pool?
Bitcoin's developer documentation distinguishes solo mining from pooled mining purely by reward timing and variance: a solo miner who finds a block keeps the full block subsidy and transaction fees, but faces long and highly irregular intervals between successful blocks. In pooled mining, rewards are shared among participants roughly in proportion to contributed work, producing smaller but more frequent payments (developer.bitcoin.org).
A solo mining pool keeps the infrastructure of a conventional pool—Stratum connectivity, block templates, block submission, and monitoring—while changing only the payout rule: the miner whose submitted work produces the winning block receives that block's reward, typically less a stated service fee, rather than sharing it with other participants. CKPool's open-source "solo" mode documents this design directly: the username associated with the winning share receives the reward at its configured address, less any configured fee (github.com). This distinguishes a solo pool from fully independent solo mining through one's own node, since the miner still depends on the pool's connection and submission infrastructure, while retaining direct exposure to the variance of individual block discovery.
Side-by-Side Comparison
| Question | Merged mining | Solo pool mining |
|---|---|---|
| What does it change? | Whether compatible auxiliary-chain rewards may be available from the same work | How a block's reward is allocated among participants |
| Changes physical hash rate? | No | No |
| Changes block-finding probability? | No | No |
| Requires chain compatibility? | Yes, the auxiliary chain must support AuxPoW validation | No specific compatibility requirement |
| Main economic effect | Possible additional auxiliary-coin rewards, subject to pool support | Concentrated reward timing and higher variance per miner |
| Main dependency | Pool support and auxiliary-chain rules | Pool submission infrastructure and fee terms |
Can Merged Mining and Solo Pool Mining Be Combined?
Because the two features operate at different layers, nothing in principle prevents a solo pool from also supporting merged mining—the outcome depends entirely on whether the relevant chains and the specific pool implementation allow it. For readers evaluating ViaBTC specifically, it is worth noting that ViaBTC discontinued the SOLO payment method across all of its coin mining pools on May 20, 2026 (UTC+8); users previously on SOLO were migrated to PPS+, or to PPLNS where PPS+ was not available (support.viabtc.com). As a result, the current comparison for ViaBTC users is between its available pooled payout methods, not between merged mining and a selectable solo mode.
Merged mining itself remains supported under ViaBTC's current PPS+ and PPLNS methods. According to ViaBTC's Help Center documentation, BTC mining can receive proportional NMC and FB merged-mining rewards, and LTC mining can receive proportional DOGE, BELLS, PEP, and DINGO merged-mining rewards (support.viabtc.com). These coin lists reflect current product documentation and may change; miners should confirm current support before connecting hash rate to rely on a specific auxiliary coin.
Illustrative Example: Expected Time to Find a Block Solo
The variance that distinguishes solo mining is easiest to see through the mathematical expectation of time to find one block, calculated as:
E[T] = (D × 2^32) / H
where D is network difficulty and H is hash rate in hashes per second. Using a difficulty snapshot of 148.36 T as a dated illustration, the expected time to find a single Bitcoin block is approximately:
- 20.2 years at 1 PH/s
- 101.0 years at 200 TH/s
- 3,365.3 years at 6 TH/s
These figures are mathematical expectations under a fixed, point-in-time difficulty, not forecasts or maximum waiting times. Actual block discovery is random—a miner could find a block much sooner or much later than the expected value—and the calculation changes at every difficulty adjustment. The figures should not be read as a judgment that a given hash rate makes solo mining "viable" or "unviable"; they illustrate why reward variance, not expected probability, is the defining characteristic of solo-pool participation.
What to Verify Before Connecting Hash Rate
Before selecting either a merged-mining setup or a solo pool, miners may want to review the following:
- Algorithm compatibility between the mining hardware and the parent chain
- Whether the intended auxiliary chain actually supports AuxPoW and whether the pool implements it
- The pool's current payout method (for example PPS+ or PPLNS) and how it interacts with merged-mining rewards
- Auxiliary-reward eligibility and settlement rules, since credited coin amounts, market value, and operating costs are separate considerations
- The pool's stated fee schedule for the chosen payout method
- Worker monitoring and failover endpoints, which affect realized uptime regardless of payout mode
- Whether the goal is steadier, more frequent payouts or direct exposure to individual block-discovery outcomes
Conclusion
Merged mining determines whether the same proof of work can be recognized by compatible chains, adding the possibility of auxiliary-chain rewards without requiring additional hashing. Solo pool mining determines who receives a block's reward and concentrates the timing and variance of that reward on the individual miner. Because these mechanisms sit at different layers of a mining setup, they should be evaluated separately, against the current documentation of the pool and chains involved, rather than treated as mutually exclusive choices.
FAQ
Does merged mining increase my hash rate or block-finding odds?
No. Merged mining does not add physical hashing power and does not change the probability of finding a parent-chain block at a given hash rate; it only determines whether a compatible auxiliary chain can also credit the same submitted work.
Is a solo mining pool the same as mining independently through my own node?
Not exactly. A solo pool still provides connectivity, block templates, and submission infrastructure; what makes it "solo" is that the miner who submits the winning work receives the block reward directly, less any stated fee, rather than sharing it with other pool participants.
Can I still use merged mining if a pool no longer offers a solo payout option?
Yes, in principle, since merged-mining eligibility depends on chain and pool support rather than on the payout method. ViaBTC, for example, currently lists merged-mining rewards as available under its PPS+ and PPLNS methods rather than a solo mode.
Are auxiliary-chain rewards guaranteed extra profit?
No. Auxiliary rewards depend on the pool's current support for that chain, its distribution rules, market value, and the miner's own operating costs; they should not be treated as automatic or equivalent to realized profit.
References
- Bitcoin Developer Guide, "Mining" — https://developer.bitcoin.org/devguide/mining.html
- Bitcoin Wiki, "Merged Mining Specification" — https://en.bitcoin.it/wiki/Merged_mining_specification
- ViaBTC Help Center, "What is Merged Mining" — https://support.viabtc.com/hc/en-us/articles/7207416775951-What-is-Merged-Mining
- ViaBTC Help Center, "Announcement on the Discontinuation of SOLO Payment Method for All Coins" — https://support.viabtc.com/hc/en-us/articles/16155896619151-Announcement-on-the-Discontinuation-of-SOLO-Payment-Method-for-All-Coins
- CKPool, "README-CKPOOL_MODES" — https://github.com/ckolivas/ckpool/blob/master/README-CKPOOL_MODES.md


