How to Mine DigiByte (DGB) — Full Setup Guide
Point any SHA-256 ASIC at DigiByte in four steps. Real block reward, real solo odds, and the config that works — measured on live DGB nodes, September 2026.
Mining DigiByte with a SHA-256 ASIC takes four steps: get a DGB address, point your miner at a stratum endpoint, set the username to that address, and verify shares are accepted. No firmware change, no account, no new hardware. SHA-256 is one of DigiByte’s five algorithms and carries its own difficulty — which is why a home miner wins blocks here on a timescale worth watching.
Before you start: three numbers most guides get wrong
Check any guide’s date before trusting its figures. The three that go stale fastest:
| Claim you will see | Reality, September 2026 |
|---|---|
| ”Block reward is 629 DGB” | ~251 DGB, falling about 1.1% per month |
| ”Solo mining takes years per block” | An S21 averages ~5 hours; a Bitaxe 3-4 weeks |
| ”ProgPoW will bring GPUs back” | Implemented around 2020, never shipped |
The reward figure matters most. DigiByte has no halving — the subsidy is multiplied by 0.98884 every month by consensus rule, so any hardcoded number is wrong within weeks of publication.
Step 1 — Get a DigiByte address
You need an address whose private keys you control. Two formats work:
- Legacy, starting with
D— universally supported - Native SegWit, starting with
dgb1— lower fees when you spend
Any wallet holding your own keys is fine: DigiByte Core, a mobile wallet, a hardware wallet with DGB support. On a non-custodial solo pool the block reward is paid directly into the coinbase transaction, straight to this address, with no pool balance in between.
Step 2 — Pick the algorithm your hardware can run
DigiByte runs five algorithms simultaneously, each mining about 20% of blocks with independent difficulty. Your hardware decides which one you use.
| Hardware you own | Algorithm | Notes |
|---|---|---|
| Bitcoin ASIC (Antminer, Whatsminer, Avalon, Bitaxe, NerdQAxe) | SHA-256 | Works unchanged, stock firmware |
| Litecoin/Doge ASIC | Scrypt | Same algorithm, dual-mine capable |
| FPGA | Odocrypt | Algorithm rewrites itself every 10 days |
| GPU | Scrypt | Marginal at best in 2026 |
| CPU | none | No CPU-friendly algorithm on DGB |
If you already own Bitcoin mining hardware, the choice is made: SHA-256, and the rest of this guide applies directly.
Step 3 — Decide solo or pooled
This is the decision that actually matters, and DigiByte changes the usual answer.
On Bitcoin, solo mining with home hardware is not a strategy — a Bitaxe averages roughly 14,500 years per block. On DigiByte the SHA-256 lane runs near 40 PH/s, roughly 1/25,000 of Bitcoin’s hashrate, so the same device is in range.
Expected time to a block, solo, at September 2026 difficulty:
| Hardware | Hashrate | Average per DGB block |
|---|---|---|
| Bitaxe Gamma | ~1.5 TH/s | 3 – 4 weeks |
| NerdQAxe++ | ~4.8 TH/s | ~8 days |
| Antminer S19 | ~95 TH/s | ~10 hours |
| Antminer S21 | ~200 TH/s | ~5 hours |
| Antminer S21 XP | ~270 TH/s | ~3.5 hours |
These are Poisson averages, not schedules — a Bitaxe can hit on day one or wait two months. But the expectation is measured in weeks, and that is the whole argument for solo on this chain.
The honest counterweight: a DGB block is worth about one US dollar at 2026 prices. Solo mining DGB is not an energy trade; it loses money on electricity at almost any tariff. What you get is the full coinbase, paid to your own address, on a chain that actually hands home hardware a win.
Step 4 — Configure the miner
The stratum convention matches Bitcoin exactly.
| Field | Value |
|---|---|
| URL | stratum+tcp://dgb.solofury.com:5050 |
| Failover | :5051 and :5052 |
| Encrypted | stratum+ssl://dgb.solofury.com:15050 |
| Username | YOUR_DGB_ADDRESS.worker_name |
| Password | x (ignored) |
Region prefixes work the same as on every other coin: eu-dgb, jp-dgb, lat-dgb, uk-dgb, me-dgb, afr-dgb, asia-dgb, pnw-dgb. Pick the closest one — on a chain with 15-second blocks, latency shows up in your reject rate.
Leave difficulty on the pool’s vardiff rather than forcing a static value. DigiByte retargets every single block, so a fixed diff that suits this morning can be wrong by evening.
Step 5 — Verify it is actually working
Three checks, in order.
Your miner shows accepted shares. Any firmware displays this. If shares are being submitted and accepted, the connection and the username are both correct.
Your address appears on the pool. Paste your DGB address into the pool dashboard. Hashrate should climb toward your device’s rated figure over about ten minutes — the averages need time to fill.
Your reject rate is sane. Expect roughly 1.5% on a nearby server and 2-4% on a distant one. Rejects on DGB run higher than on Bitcoin because a new job arrives every 75 seconds. This is cosmetic: your displayed hashrate reads slightly low, but a rejected share never reduces your probability of finding a block.
Common problems
| Symptom | Cause | Fix |
|---|---|---|
| Miner connects, shares rejected immediately | Invalid address in username | Verify the address starts with D or dgb1 and has no typo |
| No connection at all | Firewall or wrong port | Confirm outbound TCP 5050 is open; try :5051 |
| Hashrate reads far below spec | Averages still filling | Wait 10 minutes; check the 5-minute figure, not the 1-minute |
| Rejects above 5% | Distant server or unstable link | Switch to the nearest region prefix |
| Found a block, no coins yet | Coinbase maturity | 100 blocks, about 25 minutes on DGB |
What to expect after the first week
Three things surprise people on DigiByte specifically.
The reward shrinks while you watch. Unlike a halving there is no date to plan around. A block paying 251 DGB today pays about 248 next month.
Difficulty moves constantly. MultiShield retargets every block per algorithm, and it is asymmetric — difficulty falls up to 16% per step but rises at most 8%. A large farm arriving on SHA-256 raises the lane’s difficulty within minutes rather than over two weeks. Track it on the Network Radar.
Blocks arrive in clusters. Poisson variance is real. On our own first day of DGB production, a single S21 found six blocks in 24 hours, then went several hours with none. Neither run means anything about the hardware.
Where this fits
If you are choosing between chains rather than committing to DGB, the coin selection guide compares all six SHA-256 options by difficulty and expected block frequency. For the deeper background on why DigiByte works the way it does — the five-algorithm design, the emission schedule read from the consensus code, and the 2026 Groestl incident — see DigiByte (DGB) explained for miners.
Network figures measured on SoloFury’s own DigiByte full nodes in Atlanta, Frankfurt and Tokyo, September 2026. Reward and emission schedule read from GetBlockSubsidy in DigiByte Core v9.26.5. Price reference: CoinGecko.
Frequently Asked Questions
What is the DigiByte block reward right now?
About 251 DGB, as of September 2026. Many guides still quote 629 DGB, which was correct years ago. DigiByte has no halving: the subsidy decays roughly 1.1% every month by consensus rule, so any fixed number goes stale within weeks.
Can I mine DigiByte with a Bitcoin ASIC?
Yes, with no changes. SHA-256 is one of DigiByte's five algorithms, so a Bitaxe, NerdQAxe, Antminer, Whatsminer or Avalon works on stock firmware. You point it at a DGB stratum endpoint and use a DigiByte address as the username.
Is solo mining DigiByte realistic, or is it a lottery?
It is realistic on SHA-256 hardware. The lane runs near 40 PH/s, so an Antminer S21 averages a block roughly every five hours and a Bitaxe roughly every three to four weeks. The lottery framing comes from Bitcoin, where the same Bitaxe averages about 14,500 years.
Can I still mine DGB with a GPU?
On Scrypt yes, marginally, and on Odocrypt with an FPGA. SHA-256, Qubit and Skein are ASIC territory. Guides that promise GPU profitability are usually referencing ProgPoW, which was implemented around 2020 but never shipped.
Which DigiByte address format should I use?
Either works. Legacy addresses start with D, native SegWit with dgb1. Use a wallet where you hold the keys — on a non-custodial solo pool the coinbase pays straight to that address, so an exchange deposit address is a bad idea.
How long until I can spend a mined DGB block?
About 25 minutes. Coinbase maturity is 100 blocks, and DigiByte produces one every 15 seconds. On Bitcoin the same 100 blocks take roughly 17 hours.
Why are my rejected shares higher on DGB than on Bitcoin?
A new job arrives every 75 seconds on the SHA-256 lane, so work in progress is discarded more often. Measured on SoloFury nodes: about 1.5% on a low-latency link, 2-4% at 370 ms. Rejected shares never reduce your chance of finding a block — connect to a nearby region to keep the number down.
Which DigiByte Core version should a miner run?
v9.26.5 or later. Versions before v9.26.2 are missing the AlgoLock fix from the June 2026 Groestl incident and may fall out of consensus. If you use a pool rather than your own node, this is the pool operator's responsibility.