Volcminer D1 LTC + DOGE Merged Mining Setup Guide
VolcMiner D1 Merged Mining Setup — informational playbook for configuring a D1-class Scrypt ASIC to earn both LTC and DOGE simultaneously via AuxPoW on a properly configured pool. Single hashrate, two coins paid, one worker config. Not a fault code; the setup-quality guide that determines whether your D1 captures the merged-mining value or leaves DOGE on the table.
Informational — Monitor and address as needed
Symptoms
- D1-class miner is hashing cleanly to a Scrypt pool but you're not sure if you're earning DOGE in addition to LTC
- LTC accruing visibly in the pool dashboard but the DOGE ledger reads `0` despite thousands of submitted shares from the same worker
- Brand new to a D1 and need the canonical first-time setup: pool choice, worker format, payout addresses, fee structures, payout thresholds
- Conflicting setup guides on the internet — one says use your LTC address as the username, another says use `account.workername` — and you want the right answer per pool
- Pool docs reference `AuxPoW` or `merged mining` and you want a plain-English explanation of what it costs (nothing) and what it pays (both coins)
- D1 has been hashing for a week and DOGE payouts haven't hit the pool's threshold — unclear if that's config issue or low-volume reality
- Considering moving the D1 from NiceHash (BTC payout, no DOGE merge) to a real Scrypt pool to capture the DOGE value
- Want to understand Prohashing's configurable payout-coin feature and how it interacts with merged mining
- Comparing pool fee structures and want to know which pool nets the most after fees on combined LTC + DOGE value
- Configured both LTC and DOGE payout addresses but only LTC is paying — need the diagnostic checklist
- Operating multiple D1 units and want to know how to split workers across pools to diversify pool risk while still capturing merged mining
- Want a Canadian / pleb-mining angle on which pool fits a decentralization-aligned home miner stacking sats
Step-by-Step Fix
Generate a fresh `LTC` payout address in your wallet (Trezor, Ledger, Electrum-LTC, Sparrow, Exodus). Receive > Litecoin > generate a new address. Prefix should be `L` (legacy), `M` (P2SH), or `ltc1` (bech32) — all three work on every Scrypt pool. Copy the address into a notes file. Never reuse an address across coins.
Generate a fresh `DOGE` payout address in the same wallet (or in Dogecoin Core / hardware-wallet companion if multi-coin support is missing). Receive > Dogecoin > generate. Prefix should be `D`. Copy the address into your notes file alongside the LTC address. Don't paste a DOGE address into an LTC field or vice versa — pools silently fail those payouts.
Pick your primary pool based on what matters to you. For decentralization ethos: `Litecoinpool` (oldest LTC pool, payouts go directly to your wallet, no custodial intermediation). For maximum payout flexibility: `Prohashing` (configurable payout coin including BTC). For largest hashrate / lowest variance: `F2Pool` or `ViaBTC`. Avoid `NiceHash` and `Kryptex` if DOGE matters — NiceHash pays only BTC, Kryptex documents LTC-only payouts on the D1.
Register at the chosen pool. Account creation = email + password on all four (Litecoinpool, F2Pool, ViaBTC, Prohashing). Verify email, log in. Save the account ID and password to your notes file (offline, encrypted).
Configure BOTH payout addresses in the pool's account settings before pointing the miner at it. Account Settings > Payout / Wallet. Paste your LTC address into the LTC field and your DOGE address into the DOGE field. Save. This is the single most-skipped step that costs home miners real DOGE in their first month — pools accrue DOGE internally but never trigger payout if no DOGE address is configured.
Note your pool's required worker format in your notes file. F2Pool: `f2pool_account.workername` plus password `x`. ViaBTC: `viabtc_account.workername` plus any password. Litecoinpool: `pool_account.workername` plus password `1`. Prohashing: `prohashing_username.workername` plus password blank or password-arguments string (`a=scrypt,c=dogecoin,n=D1Rig`). Type the worker string into a notes file first — never paste from a phone (iOS silently injects curly quotes that break worker authentication).
Plug the D1 in. Get its IP from your router's admin page or DHCP table. Default credentials on stock VolcMiner firmware: `root` / `ltc@dog`. Change the password after first login (recommend a 20-character random string saved to your notes file).
Configure Pool 1 in the D1 Web UI with your primary pool's stratum URL, port, worker name, and password. Litecoinpool US East: `stratum+tcp://us.litecoinpool.org:3333`. F2Pool: `stratum+tcp://ltc.f2pool.com:8888`. ViaBTC: `stratum+tcp://ltc.viabtc.com:3333` (or `:25` / `:443` if your firewall blocks 3333). Prohashing: `stratum+tcp://prohashing.com:3333`. Save.
Configure Pool 2 as a different region of the same pool. Litecoinpool EU: `stratum+tcp://eu.litecoinpool.org:3333`. F2Pool's `ltc.f2pool.com:8888` resolves to multiple regions automatically; you can re-enter it or pick a regional alias. The point is that Pool 2 should catch a regional outage of your primary, not just be a duplicate. Save.
Configure Pool 3 as a completely different pool entirely as your floor coverage. If Pool 1 and Pool 2 are both down (rare but real), Pool 3 catches the hashrate. Use a second pool from your tier-1 setup (e.g., F2Pool primary + ViaBTC fallback). For maximum diversification, point Pool 3 at NiceHash for BTC floor coverage, accepting that during a Pool 3 fall-through you'd only earn BTC, no merged DOGE. Save and power-cycle the miner for 30 seconds.
Wait 5 minutes. Confirm the pool dashboard shows the worker as accepted, with a non-zero pool-side hashrate matching the local Web UI within 15 minutes. If the worker is not accepted, you have a Stratum auth issue — see the `volcminer-d1-pool-connection-failed` page first, fix that, then come back to merged-mining validation.
After 24 hours, validate both LTC and DOGE are accruing. Pool Earnings tab > LTC and DOGE line items should both be non-zero. If LTC is non-zero but DOGE is zero, recheck Step 5 — the DOGE payout address is the most common miss. If both are zero, recheck Step 6/8 — share submission isn't reaching the pool. If both are non-zero but DOGE is below threshold, just wait one more payout cycle.
Calculate effective payout vs. fee. Pool fees: Litecoinpool ~0%-2% PPS depending on tier; F2Pool ~2-4% PPS+; ViaBTC ~2-4% PPS / FPPS; Prohashing ~5%. Translate fees into your monthly LTC + DOGE net using the pool's earnings dashboard. At small home-mining volumes the absolute fee delta is small ($1-5 USD/month per pool). Don't fee-shop alone — pick on responsiveness, account ergonomics, and feature set.
Multi-miner: split workers across pools to diversify pool risk. If you operate 3 D1 units, point one at Litecoinpool primary, one at F2Pool primary, one at Prohashing primary. Each is configured for merged mining. Pool outage on any one affects only one-third of your hashrate, and you build operating familiarity with all three platforms.
Test failover by intentionally breaking Pool 1. Once everything works, change Pool 1's URL to a deliberately invalid endpoint (`stratum+tcp://example.invalid:3333`). Save. Confirm the miner falls through to Pool 2 within 90-180 seconds and Pool 2's dashboard sees the worker. If failover doesn't work, your Pool 2 config is wrong. Restore Pool 1 once verified.
When to ask D-Central for help: you've configured both addresses, the worker is authenticated, shares flow, but DOGE is consistently zero across 2+ different merge pools after 7+ days each. This is rare and points at either pool-side AuxPoW migration issues (temporary, contact pool support) or — much rarer — a control-board firmware quirk on the D1 affecting extranonce subscription / AuxPoW share validation. The latter is a Tier 4 escalation.
Capture a diagnostic bundle for D-Central support: pool dashboard screenshots showing LTC accrual + DOGE zero across the same worker, your account ID, worker name, time window, and a note describing what you've already tried. Email the bundle to D-Central support, or open a repair ticket at https://d-central.tech/services/asic-repair/ if the miner is otherwise misbehaving. Most setup-only tickets resolve in under 30 minutes by email — faster than a repair workflow.
When to Seek Professional Repair
If the steps above do not resolve the issue, or if you are not comfortable performing these repairs yourself, professional service is recommended. Attempting advanced repairs without proper equipment can cause further damage.
Related Error Codes
Still Having Issues?
Our team of Bitcoin Mining Hackers has been repairing ASIC miners since 2016. We have seen it all and fixed it all. Get a professional diagnosis.