Litecoin and Dogecoin merged mining: AuxPoW and pool rewards
Understand the AuxPoW evidence chain, why a DOGE block need not coincide with an LTC block, and how to account for separate coin rewards and shared electricity.
Conceptual diagram · blocks need not be accepted simultaneously.
On this page
Dotted-underlined terms open a quick definition. Close it to keep reading.
lets a compatible stream of work support and Dogecoin while each chain retains its own , transactions, balances and . It does not merge the coins, require every DOGE block to coincide with an LTC block, or promise that a miner receives every auxiliary reward.
Expanded review · 22 October 2026. Technical references are pinned to Litecoin Core 0.21.5.8 and Dogecoin Core 1.14.9. The target and revenue examples are synthetic calculations, not captured jobs, observed or payout forecasts.
How one stream of work serves two chains
In this relationship Litecoin supplies the parent mining work, and Dogecoin accepts auxiliary proof of work, or AuxPoW. A pool constructs an auxiliary candidate and commits to it through the parent . Its miners search parent headers using Scrypt. A qualifying result can then be submitted with evidence linking that work to the auxiliary candidate.
Conceptual AuxPoW workflow; one DOGE block need not coincide with an LTC block. Values and explanations are also provided in the text.
It helps to separate the links in that evidence:
The auxiliary block hash is linked, possibly through an auxiliary-chain , to a committed auxiliary root.
That root appears in the parent coinbase's input script, together with auxiliary-tree parameters.
A separate parent-transaction Merkle branch links the coinbase to the parent header's Merkle root.
The parent header supplies the result tested against the auxiliary block's target.
These are two different Merkle relationships: auxiliary candidate to commitment, then parent coinbase to parent header. A proof is more than a claim that two pools used the same algorithm. Dogecoin's AuxPoW validator checks commitment placement, the coinbase branch, chain-tree size and the deterministic index. Its data structures define the merged-mining marker as bytes fa be 6d 6d.
That marker is not a complete proof. The implementation also has a historical compatibility path for certain commitments without it. Neither a miner screenshot nor the presence of those four bytes establishes that a candidate satisfies all consensus checks.
Separate targets: why a DOGE block need not be an LTC block
A proof-of-work target is a numeric upper bound: a smaller target is harder to meet. Each chain determines its own target. The pool's share target is a third threshold used for accounting; ordinary accepted shares are usually far easier to find than network blocks.
Synthetic reduced-number example: parent target 100, auxiliary target 400; these are not real 256-bit targets.
Assumed work result
Target comparison
What could be submitted
80
80 ≤ 100 and 80 ≤ 400
Qualifies for both work thresholds
250
250 > 100 but 250 ≤ 400
Auxiliary work threshold only
500
500 > both targets
Neither network block threshold
All rows still assume the required commitment, current templates and other validity rules. A threshold match alone does not guarantee block acceptance or survival in the active chain. If the targets had the opposite ordering, a result could meet the parent target without meeting the auxiliary target. Never infer today's ordering from this illustration.
The auxiliary proof uses the parent header as evidence; it does not require that header to become an accepted Litecoin block. The auxiliary chain can therefore accept work that fails Litecoin's harder threshold in the second row. Its own block validation, parent-work selection and work-target checks remain relevant. There is no rule that a DOGE block must wait for the next LTC .
When Dogecoin adopted AuxPoW
Dogecoin's AuxPoW activation occurred at block 371,337 on 11 September 2014. The 1.8.0 software release preceded that activation on 24 August. These are different events. The dates and activation boundary are documented in the maintainer's 1.8.x retrospective.
A history should distinguish software availability, a consensus activation height and later implementation changes. The retrospective also discusses later compatibility problems; a simple “merged in 2014” timeline is not a complete account of every release's behavior. Our documented fork and code-history guide makes the same distinction.
Shared work, different rules
Selected mainnet rules in the pinned versions; target times are averages, not clocks.
10,000 DOGE ongoing subsidy in the current schedule
Current LTC subsidy era
6.25 LTC at heights 2,520,000–3,359,999
No matching LTC-style halving
Ledger and payment destination
Litecoin transactions and scripts
Dogecoin transactions and scripts
See Litecoin parameters, Dogecoin parameters and the Dogecoin subsidy function. At target spacing, the schedules imply 576 LTC blocks and 1,440 DOGE blocks per day: 3,600 LTC in the stated era and 14.4 million DOGE in subsidy. The latter annualizes to 5.256 billion DOGE over 365 days. Actual block counts vary.
An balance does not acquire DOGE through this relationship. Consensus upgrades, fees, wallet compatibility and supply rules remain chain-specific. A Litecoin transaction cannot move DOGE merely because a pool mines both chains.
Why it matters to mining economics
Calculate expected coins separately for each chain before adding their values in one currency. The assumed network work rate must correspond to that chain. Using Litecoin's hashrate as Dogecoin's denominator without justification can distort the estimate.
For an explicit teaching case, assume a miner delivers 16 GH/s continuously and both networks have an effective 3 PH/s of relevant Scrypt work. Assume target block counts, constant difficulty, the subsidy era above, no transaction fees and no other auxiliary coins. These are scenario inputs, not current network observations.
If a hypothetical operator deducted 2% separately from both theoretical subsidy streams, the modeled credits would be 0.018816 LTC and 75.264 DOGE per day. This is not a quote for any pool: real ratios, additional coins, fees and accounting can differ.
Hypothetical valuation after those illustrative 2% deductions; no live prices.
Modeled credit
Assumed price
Value per day
0.018816 LTC
$60 per LTC
$1.12896
75.264 DOGE
$0.10 per DOGE
$7.52640
Combined modeled revenue
Same currency and period
$8.65536 before operating costs
Now assume 3.36 kW continuous wall power at $0.10/kWh. Electricity costs 3.36 × 24 × 0.10 = $8.064/day, leaving $0.59136 before cooling, maintenance, hardware cost, conversion, taxes and other costs. A small change in an assumption can remove that margin. The calculation is reproducible in the downloadable model; it is not evidence that a particular machine is profitable.
Count the miner's electricity once for this shared hashing stream. Adding two separate estimates for the same device's power would double count it. , pool infrastructure and networking still have overhead. The energy guide explains why shared work does not produce a unique physical allocation of all electricity between coins.
A pool checklist before connecting hardware
Ask which chains are actually credited, which assets leave the pool, and how the operator calculates each balance. A pool can pay LTC and DOGE separately, convert proceeds, or include some auxiliary revenue in a reward ratio. Protocol compatibility does not dictate that commercial agreement.
On 22 October 2026, LitecoinPool's own help page described separate LTC and DOGE payout destinations and stated that other auxiliary proceeds support its PPS ratio rather than being distributed as every underlying coin. That is a dated operator declaration, not an independent payout audit or a market-wide rule.
Record per-coin fees, conversion spreads, withdrawal conditions, stale-share treatment and outstanding balances. Confirm that you control the intended LTC and DOGE destinations; one is not interchangeable between them. Reconcile actual receipts rather than treating a combined dashboard estimate as settled revenue. The pool-selection guide adds a ledger and a PPS/PPLNS comparison.
What merged mining does not guarantee
Sharing work does not guarantee equal security, independent mining populations, a price floor or twice the profit. Operator participation, block-template control, software validation and each chain's economic incentives still matter. Adding reported hashrates can also count the same hardware twice; do not describe that sum as independent computing power.
An LTC changes the LTC subsidy component. In the hypothetical case above, halving only that component would reduce total pre-fee subsidy value from $8.832 to $8.256/day, about 6.52%, while holding all prices, work rates and DOGE rules fixed. It would not halve the modeled combined revenue. Real difficulty, participation and prices can change, so this is a sensitivity calculation rather than a forecast.
Must an LTC block exist for every DOGE AuxPoW block?
No. The auxiliary proof can use a parent header that meets Dogecoin's target without becoming an accepted Litecoin block.
Does merged mining send DOGE to my LTC address?
No. The ledgers and destinations remain separate. Follow the pool's supported payout routes for each asset.
Do all Scrypt pools pay every auxiliary coin?
No. The operator's reward rules determine what is credited, converted or included in a payout ratio. Inspect the current terms.
Does a valid pool share mean I found a network block?
Usually not. Share targets serve pool accounting and are generally easier than network block targets.
Should I double the miner's electricity for LTC and DOGE?
No. Count the same device's measured electricity once for its shared hashing operation, while accounting separately for other infrastructure.
Does an LTC halving halve combined LTC and DOGE revenue?
Not mechanically. It changes the LTC subsidy component. Combined revenue also depends on DOGE, fees, prices, difficulty and the pool's accounting.
Merge Mining
In brief Reusing proof-of-work calculations across compatible chains, without merging their records or guaranteeing extra payouts.
Reusing proof-of-work computations for compatible chains, such as Litecoin mining alongside Dogecoin auxiliary proof of work. Pool support, fees and payout rules determine what a miner actually receives.
For example A compatible pool can use Litecoin mining work for Dogecoin too, then distribute rewards under its own payout rules.
Common mistake Assuming merged rewards are automatic for every miner or that two chains become one shared ledger.
In brief The hashing method used for Litecoin mining; Scrypt and Bitcoin's SHA-256 mining hardware are not interchangeable.
A memory-hard key-derivation function also used in Litecoin's proof-of-work hashing. Litecoin uses a particular Scrypt configuration rather than Bitcoin's double-SHA-256 mining algorithm. Specialized Scrypt ASICs exist, so memory-hard does not mean ASIC-proof.
For example A Litecoin miner needs Scrypt-compatible hardware; a SHA-256 Bitcoin miner does different work.
Common mistake Assuming the algorithm means current Litecoin mining is practical or profitable on an ordinary laptop.
In brief A peer-to-peer cryptocurrency with its own Scrypt proof-of-work network and a maximum issuance of 84 million LTC.
A peer-to-peer cryptocurrency launched in 2011. Litecoin uses Scrypt proof of work, targets an average 2.5-minute block interval and has an issuance schedule capped at 84 million LTC. Individual block times and payment acceptance times vary.
For example Sending 0.1 LTC on Litecoin transfers a fraction of one coin; you do not need to buy a whole LTC first.
Common mistake Assuming a token with LTC in its name on another network is automatically native Litecoin.
In brief A group of transactions linked to the previous block under the network's rules.
A batch of transactions accepted under the network rules and linked to the previous block. Litecoin targets one new block every 2.5 minutes on average; a particular block may arrive sooner or much later.
For example Your payment may wait unconfirmed and then receive its first confirmation when a miner includes it in an accepted block.
Common mistake Treating the 2.5-minute target as a countdown or a maximum wait for your payment.
In brief The rules nodes use to check transactions and blocks, with Litecoin using proof of work to choose among valid chains.
Rules used by nodes to decide which transactions and blocks are valid. Litecoin uses proof of work to select among valid chains. Miners propose blocks, but validating nodes also enforce the rules.
For example A full node rejects a block that breaks its validation rules even when a miner has done proof-of-work calculations.
Common mistake Thinking that miners can make any transaction valid merely by including it in a block.
In brief Searching for valid proof of work and proposing Litecoin blocks that other nodes independently check.
Searching for proof of work and assembling candidate blocks that follow a network's rules. Validating nodes independently check proposed blocks. An accepted Litecoin block can pay its miner the permitted subsidy and transaction fees; a pool participant is paid under the pool's scheme.
For example An ASIC connected to a pool contributes proof-of-work attempts; the pool pays according to its published scheme.
Common mistake Comparing coin revenue without subtracting electricity, pool charges, downtime and equipment costs.
In brief The rate of proof-of-work attempts; a network-wide figure is estimated and depends on the calculation method.
The rate of proof-of-work hash attempts, usually expressed per second. Network hash rate is estimated from blocks and difficulty rather than directly counted. Compare figures for the same algorithm; a higher rate alone does not establish decentralization or mining profitability.
For example One PH/s represents one quadrillion hash attempts per second; compare only figures for the relevant mining algorithm.
Common mistake Comparing Litecoin and Bitcoin hash-rate numbers as if Scrypt and SHA-256 work had identical costs.
In brief A block's special first transaction, used to claim newly created LTC and fees rather than spend ordinary earlier outputs.
The special first transaction in a block through which its creator can claim the allowed block subsidy and transaction fees. It does not spend ordinary previous outputs. Its spendable outputs are subject to coinbase maturity. This protocol term is separate from the similarly named exchange.
For example A block explorer shows a mining reward in the block's coinbase transaction. A later pool payout can be an ordinary transaction spending matured coins.
Common mistake Assuming an exchange withdrawal is a coinbase transaction because of the service's name, or treating newly mined outputs as immediately spendable.
In brief A hash-based proof of a transparent transaction's inclusion in a block, which alone does not establish the accepted chain.
For an ordinary transparent transaction, a proof can show that its TXID is committed by a particular block's Merkle root. Matching a root alone does not prove that the block belongs to the accepted chain or that an expected recipient was paid. Those need separate checks.
For example A proof can match a supplied header while you still need to verify the header's chain context and inspect the payment outputs.
Common mistake Treating a successful hash calculation as proof of chain membership, current spendable funds or a service's credited deposit.
In brief A system where miners compete to find valid hash results, while nodes independently check the resulting blocks.
A system in which miners search for a hash satisfying a network difficulty target. Litecoin uses Scrypt for this work; Bitcoin uses double SHA-256. Validating nodes still check all the block's rules, not only its proof of work.
For example A miner searches for valid work, while nodes check that the resulting block also follows the transaction and consensus rules.
Common mistake Thinking proof of work alone lets a miner spend someone else's coins or choose any subsidy amount.
In brief A transaction gains confirmations as blocks build on its inclusion, but those confirmations can fall if chain history changes.
A transaction receives its first confirmation when included in a block in the accepted chain. Each block then built on top adds another. A chain reorganization can reduce or remove the count. The recipient decides how many confirmations it requires. Litecoin targets an average 2.5-minute block interval; individual blocks can arrive sooner or much later.
For example A transaction in the latest accepted block has one confirmation; the next block raises that count to two.
Common mistake Confusing a wallet's sent message, a TXID or mempool visibility with the first confirmation.
In brief Software or a device for managing wallet keys and payments, though a watch-only setup cannot sign on its own.
Software or a device that manages keys and helps you receive and send Litecoin. Coins are recorded on the blockchain. A watch-only wallet can show addresses and transactions without holding the keys needed to spend.
For example One wallet can generate several receiving addresses and still show them as a single combined balance.
Common mistake Thinking coins live inside the app, or that seeing a balance proves that the wallet can sign a spend.
In brief A service that coordinates miners' work and pays them under its own reward scheme and fee rules.
A service that coordinates mining work and pays participants according to its reward scheme. Fee handling, payment timing, variance and the treatment of merged-mining rewards depend on the operator's rules.
For example A pool can make payouts more regular than solo mining, but its fees and payment scheme affect the result.
Common mistake Assuming all pools pay the same amount for the same displayed hash rate or include the same merged rewards.
In brief A participant running network software; a full node checks rules but need not keep all old block files.
A participant running network software. A full node independently validates rules; a pruned full node can discard older block files after validation. Not every node stores the complete historical blockchain.
For example A pruned full node checks the chain but later discards old block files to reduce disk use.
Common mistake Assuming every node is a miner, or that pruning means it skipped consensus validation.
In brief An encoded payment destination whose network, owner and wallet compatibility still need checking.
An encoded destination for a payment. Common transparent Litecoin addresses begin with L, M or ltc1; MWEB uses a different address format. An address is not a bank account or proof of identity. Check network and wallet compatibility before sending.
For example To receive LTC, copy a Litecoin receiving address from your wallet and check it against the address shown to the sender.
Common mistake A valid-looking address does not prove that it belongs to the intended person or uses the network the sender selected.
In brief A scheduled cut by half in newly created LTC per block, without halving existing balances or the transaction-fee component.
A scheduled cut in the block subsidy: the new LTC a miner can create in a block. Litecoin mainnet halves this subsidy every 840,000 blocks, roughly four years. Transaction fees are separate and are not halved by this rule.
For example At height 3,360,000, Litecoin's scheduled subsidy changes from 6.25 LTC to 3.125 LTC per block; transaction fees remain separate.
Common mistake Assuming the event halves your wallet balance or guarantees that the market price will rise.
Content review recorded: 2026-10-22. The review record does not identify a separate independent reviewer. An edited date above records an edit, not a new fact-check. AI-assisted editing or new artwork alone does not complete a source review.
Editor-in-chief of Litecoin.watch and founder of MyBank.pl. His published work covers foreign exchange, financial education and Litecoin. On Litecoin.watch, his remit includes editorial direction, source transparency and the practical guides and research published by the site.