DigiByte (DGB)

If you are having issues syncing DigiByte v9.26.2 make your digibyte.conf in the default $DGB data directory look like this:

========================================
[main]
server=1
listen=1
txindex=1
digidollar=1
minimumchainwork=00

addnode=https://t.co/XsdLBtgXrv
addnode=https://t.co/lWADpzDpaE
addnode=https://t.co/zxSoIEed1K
========================================

There was an incorrect minimumchainwork setting added in v9.26.2 release that will be fixed shortly with v9.26.3.

We manually confirmed adding 'minimumchainwork=00' to digibyte.conf fixes sync issue, it was not peers, it was not v7 nodes on wrong chain.

The issue was minimumchainwork was added in BTC v25 and does not apply to DGB multialgo.

We calculated a recent block 23.5 million chain work for v9.26.2 and it only adds up to 28% in pre-sync and resets because the check is not properly adapted to DGB multi algo.

So we return to same default setting for what we had in v7 and v8.

DigiByte Groestl Mining Incident — Forensic $DGB Update (2026-06-30)

The rouge miner who reactivated the retired Groestl algorithm with a modified DGB core wallet has stopped. They mined for roughly 35 hours. Earning around $900 in DGB mining rewards.

Full data, scanned block-by-block from the incident onset (block 23,751,096) to 23,766,084:

Rouge miner totals: 1,514 Groestl blocks · 392,616.56 DGB
-dgb1qy5epvfs535a96tygn945a3a85lauh3ddu9v63y — coinbase tag SORG — 922 blocks · 239,093 DGB

-D8S5JWaCrpFsryGG1c9AzWKhbS7e7VZ4r8 — 592 blocks · 153,524 DGB

- Active 2026-06-28 16:40:05 → 2026-06-30 04:21:05 UTC, then stopped.

No rouge miner Groestl block since
(≈4,850 blocks).

What ended it: legitimate pools turned on Groestl. zpool (/zpool.ca/, address
DC42uvyywWHgK4yob7a8Yu4mnE5evYw8xs) began mining it at 04:09 UTC; Groestl difficulty climbed ~5× (from the floor to ~4,500), and the rouge miner quit ~12 minutes later — priced out.

DigiHash (/DigiHashV2/) have also joined.

zpool and DigiHash are legitimate pools, NOT the rouge miner.

Full Groestl breakdown (2,323 blocks since onset):
- Attacker: 1,514 blocks / 392,617 DGB (stopped)
- zpool: 808 blocks / 209,545 DGB (now dominant)
- DigiHash: 1 block / 259 DGB (just joined)

Status: Groestl is still being mined (by pools now, not the attacker), so block times remain ~12.5s and a 6th algorithm is effectively active.

The permanent fix is DigiByte Core v9.26.2, whose algolock rejects all Groestl (and any retired/unknown algorithm) at block 23,808,000. Everyone must upgrade to v9.26.2 before then within 7 days.

This rouge miner likely may have spent more on AI tokens figuring out the mining vector than the $900 they earned in mining rewards.

So we should thank them for helping us make DGB more secure & giving people a reason to upgrade to $DGB #DigiDollar!

We also proved adding a 6th mining algorithm makes DGB even more decentralized & DigiShield successfully prevented a 51% attack and works with 6 algos. 👍

If you are having issues syncing your new $DGB v9.26.2 please add the following to your digibyte.conf file:

addnode=https://t.co/8YCntZKa8N
addnode=https://t.co/5gdPR1NrbW
addnode=https://t.co/96gswPzvjS