DigiByte Discussion

30 June 2026 20:08

The network is currently undergoing an important update, I think that in time it will be stable and you can try my pool for your needs!

DigiByte Discussion

30 June 2026 20:02

I have but its under upgrade to new version now

DigiByte Discussion

30 June 2026 19:58

Do not speak to anyone in DM, even if it looks legit

DigiByte Discussion

30 June 2026 19:56

Hi all, I upgraded my node to 9.26.2, did a full restart + reindex=1, but I still have the same old height and stuck at the same block. How can I join the new network?

UpdateTip: new best=b3e5b559b5d731ec10376ef1b34e89e9ebf8cc356a9cf328c27d768e3cd663d0 height=23762760 version=0x20000002 log2_work=84.860609 tx=53863560 date='2026-06-30T17:48:32Z' progress=1.000000 cache=0.3MiB(1919txo)


My progress says 1, but my height is still 23,762,760 which is the old network

DigiByte Discussion

30 June 2026 19:52

so I’m looking for a private or hobby pool. Any stratum address available?

DigiByte Discussion

30 June 2026 19:51

sol, I’m looking for a small DigiByte SHA‑256 solo pool with *low fixed difficulty* that accepts micro‑miners (Bitaxe). Public pools are unstable today, so I’m looking for a private or hobby pool. Any stratum address available?

DigiByte Discussion

30 June 2026 19:48

ok i have joined now?

DigiByte Discussion

30 June 2026 12:25

I've just released a new version of BoxWallet that supports DigiByte 9.26.2

DigiByte Discussion

30 June 2026 06:51

I'll get this added into BoxWallet today.

DigiByte Discussion

30 June 2026 04:07

The Groestl incident has been shared for everyone to read, it details how it happened a line of code that was left in instead of being removed during the v8 upgrade. It also talks about how someone used AI to find it. I share this to keep people in this discussion informed and aware.

DigiByte Discussion

30 June 2026 03:46

Honestly i wouldn't believe him no matter what he said. He is very lose with the truth and why would someone put the expense in to doing this exploit if they arent going to take advantage. There blocks would obviously get rewound so it makes sense to use those blocks to double spend.

DigiByte Discussion

30 June 2026 03:41

Has he actually analysed the thousands of blocks created in the fork to confirm no funds where taken?

DigiByte Discussion

29 June 2026 22:48

The fix to all of this will be 9.26.2 which is DigiDollar

DigiByte Discussion

29 June 2026 21:06

Nah there is nothing added to code since 7.17.3 that required people to upgrade so only testers should have upgraded.

DigiByte Discussion

29 June 2026 21:04

About this incident, I suggest communicate with the core developers because they may be working on a fix and telling people to switch to 7.17.3 could create more unnecessary disruptions.

DigiByte Discussion

30 June 2026 20:02

okay no help here i guess

DigiByte Discussion

30 June 2026 20:01

Does anyone have a DigiByte SHA‑256 *solo pool* with *low fixed difficulty*? I’m using a Bitaxe micro‑miner, so I need a pool that accepts low hashrate and no TLS. A private or hobby pool would be perfect. Any stratum address available?

DigiByte Discussion

30 June 2026 19:56

Should I delete /blocks folder and start again?

DigiByte Discussion

30 June 2026 19:52

Yeah, I don't like your flooding. Roald has been temporarily muted for 4 minutes.

DigiByte Discussion

30 June 2026 19:52

so my mine tis nit accepted anymore

DigiByte Discussion

30 June 2026 19:50

my normal bitaxe miner as of today is nit longer accepted and the big pools

DigiByte Discussion

30 June 2026 12:25

https://codeberg.org/richardltc/BoxWallet

DigiByte Discussion

30 June 2026 07:16

https://github.com/DigiByte-Core/digibyte/releases/tag/v9.26.2

DigiByte Discussion

30 June 2026 04:39

DigiByte Community Update: v9.26.2 Release Incoming (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 ~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!

DigiByte Discussion

30 June 2026 03:47

Anyone have a copy of both chain histories? If so I will write a script to verify the claims.

DigiByte Discussion

30 June 2026 03:43

Go to the GitHub ask or make a comment: https://github.com/DigiByte-Core/digibyte/pull/416

DigiByte Discussion

30 June 2026 03:32

DigiByte Community Update: Groestl Mining Incident & v9.26.2 Fix (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 ~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.

DigiByte Discussion

29 June 2026 21:13

I don’t want to speak about things that I know nothing about, so I won’t but there is an open PR which is public for anyone to see, the point I’m trying to make is we should wait to get a better idea of what happened, what steps to take next from the core developers.

DigiByte Discussion

29 June 2026 21:04

So bug is old enough to effect 7.17.3? Only a few nodes that i have tried but they would not connect to the hacked chain.

DigiByte Discussion

29 June 2026 21:02

Downgrading won't help