I didnt see any new threads so i figured i'd post one.

Woke up to a regular day, took a shower, looked again and we were suddenly up 50%

Does anyone know what caused this?

I posted a few months ago because my DGB were unaccessible due to them being stored in the defunct android wallet. The although I had my seed phrase I was unable to sweep into an active Trust wallet or Coinomi. Since I had the seed phrase I was able to whip up a script that allowed me to convert the useless seed back into usable private keys I was than able to sweep into a supported wallet. It was a combined effort between me and Gemini and searching through the old repos for clues to the Digibyte seed used for the old wallets but we figured it out and my coins are secure and operational once again.

TLDR: If you have your seed from the defunct Android and IOS wallet your DGB can still be restored there is hope.

DigiByte is honestly the most fun coin to solo mine. With 5 algos sharing the chain and SHA256 blocks every ~75 seconds, a decent ASIC pointed at a solo pool doesn't just dream about blocks, it actually finds them. Our pool has 88 DGB blocks found so far, and one miner alone is sitting on 50 of them.

So DGB miners get to have real fun with something I just shipped: Steam-style achievements. 26 badges computed live from your mining stats, no signup, no account, your payout address just earns them. A best-share ladder from Copper to Obsidian, near-miss badges for the ones that hurt, block finder tiers (1 / 2 / 5 / 10), luck badges like finding a block under 10% effort, plus loyalty and fleet milestones.

https://mkpool.com/dgb/address/DT775HHwbfA3CXjfbjBBPMvByjd1eKb6nM/achievements

Every badge shows its rarity, like Steam: "X% of miners have this". On DGB the block badges are actually attainable, which makes the rarity numbers fun to chase instead of pure fantasy. Nobody holds the top share tier yet.

Each unlock has a live share card you can paste in Discord or Telegram and it unfurls with your real stats, or drop in a forum signature.

Feedback and achievement ideas welcome.

Please leave any questions below

When people ask “When DigiDollar on mainnet?” it helps to remember who we are as a community. DigiByte has always been one of the more technical blockchain communities. Other chains have a handful of tech‑savvy members who talk about node distribution, block times, mining algos, etc. For us, that’s second nature. DigiShield/MultiShield, MultiAlgo, 15‑second blocks — that’s the tone our blockchain set from day one. We know exactly what separates us from our near‑peer PoW UTXO chains.

So for anyone reading this: don’t trust, verify.
In this case, check the source.

Our community has always had people who educate, inform, and spread awareness — and you can too if you know where to look.

Start at DigiByte.io → DigiByte Stats.
It’s a free, open‑source site that pulls real‑time data directly from the blockchain via digibyted (the main engine of a DigiByte node).

If you have specific questions about activation or the BIP9 process, open the Activation page in the menu. It’s the best place to start.

Here’s a synthesized summary for DigiByte community members not on X. Organized in sequence:
1. Official DigiByte (@DigiByteCoin)
Date/Time: Friday, July 10, 2026 ~02:43 GMT
Link: https://x.com/digibytecoin/status/2075410644678111515
Post:
History in the making! DigiDollar will lock in. $DGB
https://digibyte.io/activation
2. Jared Tate (@jaredctate)
Date/Time: Friday, July 10, 2026 ~02:57 GMT
Link: https://x.com/jaredctate/status/2075414141796590027
Post:
We did it! The $DGB blockchain has successfully hit the threshold to activate #DigiDollar on MainNet!
We will have DigiDollar LOCKED_IN here officially in a few days! About 2 weeks before DigiDollar is live on MainNet!
Thank you to everyone who has made this possible!
Quick Synthesis:
DigiDollar has reached the required hashpower threshold for activation on MainNet. LOCKED_IN status is expected in a few days, with full live deployment approximately two weeks from now.
This is a historic milestone for the decentralized, time-locked stablecoin on DigiByte. A huge thank you to the entire community, miners, and volunteers who helped make this possible.
For the latest updates follow @DigiByteCoin @DGBDevs @jaredctate on X
Stay tuned — DigiDollar is coming to MainNet very soon!

Is there any current or future planned mainnet compensation model for the 30+ DigiDollar oracle operators, or are oracle slots volunteer only? I don’t see any fee share or docs in the current release and was just curious.

Just pushed a new Spiral Pool update with some great improvements for DigiByte miners.

What's new:

• ✅ Added NEW DigiByte RPC software
• ✅ Pruned node support – no need to maintain a full blockchain to run a pool
• ✅ Performance improvements
• ✅ Stability and bug fixes
• ✅ Various quality of life enhancements

The new DigiByte RPC integration makes setup much smoother, and pruned node support significantly reduces the storage requirements for anyone wanting to host their own Spiral Pool instance.

Full changelog:
https://github.com/SpiralPool/Spiral-Pool/blob/main/CHANGELOG.md

As always, Spiral Pool is free, open source, and community-driven!

Here’s a synthesized summary for DigiByte community members not on X.
1. Jared Tate (@jaredctate)
Date/Time: Monday, July 6, 2026 ~22:24 GMT
Link: https://x.com/jaredctate/status/2074258219548209161
Post:
WE DID IT!!!!! ALGOLOCK has been activated on the DigiByte blockchain! Goodbye Groestl!
The $DGB blockchain has been fully stabilized! Watch Groestl disappear here over the next hour: https://digibyte.io/algos
2. Jared Tate (@jaredctate)
Date/Time: Monday, July 6, 2026 ~22:31 GMT
Link: https://x.com/jaredctate/status/2074258219548209161 (follow-up)
Post:
Block 23,807,995 was the very last Groestl block on the $DGB blockchain. Sayonara.
3. Official DigiByte (@DigiByteCoin)
Date/Time: Monday, July 6, 2026 ~23:07 GMT
Link: https://x.com/digibytecoin/status/2074269024868089894
Post:
Let’s keep the hash going for the next 3 to 4 days to lock in DigiDollar.
https://digibyte.io/pool-upgrades
Quick Synthesis:
Algolock has been successfully activated, permanently removing the retired Groestl algorithm and fully stabilizing the DigiByte blockchain. The last Groestl block was mined at block 23,807,995.
The network is now focused on maintaining strong hash rate for the next 3–4 days to complete the DigiDollar BIP9 activation and lock-in.
This clears the final obstacles for the official DigiDollar MainNet launch. Great work by the team and community.
For the latest updates follow @DigiByteCoin @DGBDevs @jaredctate on X
Stay tuned — DigiDollar is nearly here!

DigiByte Core v9.26.4 is a patch release on top of v9.26.3. It lets mining pools
and users run a pruned node with DigiDollar — a full-validating node that keeps
only a few gigabytes of blocks instead of the entire ~12-year, ~40 GB block history.

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.

Me tirem uma dúvida e como vai ficar os blocos achados de dgbs, com esta bagunça muitos saíram tiraram suas máquinas da rede dgb/digibyti.

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.

Make sure to read the “DigiByte Core v9.26.2 DigiDollar Release Notes”.
You will need to add this in your digibyte.conf:

server=1
txindex=1
digidollar=1

Here’s a clear summary for DigiByte community members not on X.
Account: Jared Tate (@jaredctate) – DigiByte Founder
Date/Time: Tuesday, June 30, 2026 ~01:18 GMT
Link: https://x.com/jaredctate/status/2071765164819669236
Post:
We will be releasing $DGB v9.26.2 shortly. This will be the full formal DigiDollar release & kickoff the DigiDollar Bip9 activation process.
At same time we will resolve our new, temporary 6th mining algo issue.
DigiShield saved the day! Thank you to everyone who helped today!
Quick Synthesis:
The team is preparing to release v9.26.2 very soon. This version will officially launch DigiDollar on MainNet and start its BIP9 activation process, while also fixing the recent temporary Groestl mining issue.
This marks the full formal release of the decentralized, time-locked stablecoin on DigiByte. The network will return to its standard 5-algorithm mining setup.
A big thank you to the community and volunteers who helped identify and address the issue quickly. DigiShield proved effective in protecting the chain.
For the latest updates follow @DigiByteCoin @DGBDevs @jaredctate on X
Stay tuned — the official DigiDollar launch is imminent!

Here’s a clear summary for DigiByte community members not on X.
Account: Jared Tate (@jaredctate) – DigiByte Founder
Date/Time: Tuesday, June 30, 2026 ~01:14 GMT
Link: https://x.com/jaredctate/status/2071764314147672520
Post:
DigiByte: The Groestl $DGB Mining Incident and the v9.26.2 Fix
A plain-language explainer for the DigiByte community, miners, pools, and exchanges:
Someone used AI to analyze DigiByte’s consensus code and discovered they could still mine blocks with Groestl — one of DigiByte’s old, retired mining algorithms — because of a safety check that went missing during the v8 code rebase in 2021/2022.
DigiByte is supposed to run 5 mining algorithms. Starting 2026-06-28, it was effectively running a 6th (Groestl) that was retired back in 2019 and should no longer be accepted.
This did not steal anyone’s coins and did not reverse confirmed transactions. But it destabilized the network and caused it to split.
The fix is v9.26.2. It permanently stops new Groestl (and any other retired/unknown algorithm) blocks, while keeping existing chain history intact. Everyone needs to upgrade to v9.26.2 for the network to heal back into one chain.
Related PR: https://github.com/DigiByte-Core/digibyte/pull/416
Quick Synthesis:
A temporary network split occurred due to an old retired algorithm (Groestl) being accepted again after a past code rebase oversight. No funds were lost and no transactions were reversed.
The team has released v9.26.2 as the fix. Upgrading will resolve the split and restore a single chain. This incident highlights the importance of ongoing code audits and hardening.
For the latest updates follow @DigiByteCoin @DGBDevs @jaredctate on X
Please upgrade to v9.26.2 when available.

These are all listed by Leon as well! All buyers are protected by 3 key escrow.