

DigiByte Community Update: Groestl Mining Incident Follow-Up (June 30, 2026)
Here’s a clear summary for DigiByte community members not on X.
Account: Jared Tate (@jaredctate) – DigiByte Founder
Date/Time: Tuesday, June 30, 2026 ~21:52 GMT
Link: https://x.com/jaredctate/status/2072075739084783823
Post:
DigiByte Groestl Mining Incident — Forensic $DGB Update (2026-06-30)
The rogue 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:
Rogue miner totals: 1,514 Groestl blocks · 392,616.56 DGB
No rogue miner Groestl block since (≈4,850 blocks).
What ended it: legitimate pools turned on Groestl. zpool and DigiHash joined, difficulty climbed ~5×, and the rogue miner quit — priced out.
DigiShield saved the day. v9.26.2 resolves all of this & brings us $DGB DigiDollar!
Quick Synthesis:
The rogue miner has stopped. No rogue Groestl blocks have been mined since approximately 4,850 blocks ago (read original post). Legitimate pools have now taken over Groestl mining, increasing difficulty and decentralizing the network further.
v9.26.3 will permanently fix the issue and deliver the full DigiDollar release. This incident ultimately accelerates upgrades across the ecosystem.
For the latest updates follow @DigiByteCoin @DGBDevs @jaredctate on X
Please upgrade to v9.26.3.
DigiByte Community Update: Groestl Mining Incident Update (June 30, 2026)
Here’s a clear summary for DigiByte community members not on X.
Account: Jared Tate (@jaredctate) – DigiByte Founder
Date/Time: Tuesday, June 30, 2026 ~18:04 GMT
Link: https://x.com/jaredctate/status/2071765164819669236
Post:
$DGB Groestl Mining Incident update:
We have been trying to mine groestl ourselves, and we figured out that we did indeed have most of the protections in $DGB core, as you can’t mine Groestl with a v8 node by default.
So the person who figured this out is running a custom modified client built with AI.
They are running a modded client, and changed getblocktemplate to accept groestl.
The missing check in validation.cpp for v8 nodes so rest of network is accepting their modded blocks, but very old v7 nodes reject. (7 years old).. about 95% of network is running v8 nodes.
Clever clever.
Thankfully DigiShield kicked in right away, prevented 51% attack and we effectively further decentralized mining with a 6th algo. The deepest reorg was 4 blocks… less than a minute.
DigiShield saved the day. v9.26.2 resolves all of this & brings us $DGB DigiDollar!
So the blessing here is we get everyone to upgrade to v9.26.2 faster.
Quick Synthesis:
The Groestl incident was caused by a highly customized AI-assisted modified client exploiting a missing validation check. It only affected very old v7 nodes while the majority (v8+) remained protected. DigiShield successfully prevented any 51% attack.
v9.26.3 will fix the issue permanently and deliver the full formal DigiDollar release. This accelerates the needed network-wide upgrade.
For the latest updates follow @DigiByteCoin @DGBDevs @jaredctate on X
Please upgrade to v9.26.3.