Digibyte Army

#DigiDollar is now active on the $DGB blockchain!!!! 🚀🚀🚀🥳🎉

Now we wait for first oracle price bundles & miners to add DD flag to use DigiDollar!

T-Minus 22 minutes until $DGB DigiDollar activation! Watch this page for a surprise when the countdown hits 0 :) DigiByte.io/activation

Happy 4th of July everyone! Here is a quick $DGB v9.26 update about #DigiDollar Activation & the coming AlgoBlock height that kicks Groestl mining off the network on July 6th. Thank you to everyone around the world who has come together his week to move DigiByte forward! 🎇

I spent a good part of today updating the DGB stats site. The $DGB nodes page now uses 2 separate methods to identify nodes & estimate true size of the DGB blockchain. There is a new rolling 24 hour crawler for inbound & outbound nodes, check it out: DigiByte.io/nodes

If you have not upgraded your $DGB core wallet to v9.26 you need to ASAP. You have less than 24 hours before ALGOLOCK kicks Groestl off the chain. We have 75% of miners upgraded, most exchanges & services but if you are on v8 you may have issues: DigiByte.io/downloads

About 60% of peers I am seeing on various DGB nodes still have not upgraded. Even after 1000+ v9.26 downloads. DGB really is decentralized :)

When you are upgrading to $DGB v9.26.2 you need to let your wallet sync. If you haven't ran your wallet in awhile this could take anywhere from a few min to a few hours depending on your pc/internet. Let me know if anyone has any questions and I will help out best I can here:

You can download 9.26.2 here: digibyte.io/downloads

Recap: $DGB DigiDollar release was imminent so Attackers have been using AI to find potential vulnerabilities to try and attack DGB. An attacker going by SORG found a way to mine an old algo so now $DGB temporarily has 6 mining algos & faster blocks. It’s like an unintended upgrade making blocks 2-3 seconds faster & mining more decentralized. DigiShield worked & thwarted multiple attempts at a 51% attack. However older, 7 year old v7.17 nodes forked to their own independent chain. Away from majority of network. Everyone should upgrade to v9.26.2! Reindex your node after upgrade if you were running an old legacy v7.17 node. This now provides us a huge opportunity to get DigiDollar out faster & a reason to get entire blockchain to upgrade quickly.

Please help us message / email your favorite mining pool & exchanges to upgrade their $DGB Core wallet. Here is a draft message to use: Subject: Urgent DigiByte Core v9.26.2 Upgrade Required Hi, DigiByte Core v9.26.2 has been released and all mining pools, exchanges, explorers, wallets, and infrastructure providers should upgrade ASAP. This release fixes an active mining issue involving the retired Groestl algorithm. DigiByte still uses its normal five mining algorithms, and v9.26.2 adds a hard rejection rule for retired/unknown algorithms. Important: • Upgrade to DigiByte Core v9.26.2 as soon as possible. • There is roughly a 7-day upgrade window before the enforcement backstop activates at block 23,808,000. • If you are running DigiByte Core v7.17.3 or older, you will need to reindex or fully resync after upgrading so your node follows the correct unified chain. • Mining pools should update immediately and ensure they are using the block version returned by Core. • Exchanges and custodians should upgrade infrastructure and monitor deposits during the network upgrade window. Release: github.com/DigiByte-Core/dig… Thank you for helping keep DigiByte secure and stable. DigiDollar is also included in this v9 release, so this is an important upgrade for the whole DigiByte blockchain ecosystem.

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 at 16:40:05 UTC (block 23,751,096), 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: some software accepted the Groestl blocks and some rejected them, so different nodes and explorers ended up on different versions of the chain. The fix is v9.26.2. It permanently stops new Groestl (and any other retired/unknown algorithm) blocks, while keeping existing chain history intact so nobody's transactions are reversed. Everyone needs to upgrade to v9.26.2 for the network to heal back into one chain. Read more here: github.com/DigiByte-Core/dig…

Please upgrade to v9.26.2 here: github.com/DigiByte-Core/dig…