DigiByte Discussion

02 July 2026 05:48

User Victoria Schmidt has 1/3 warnings; be careful!
Reason:
Promotion of other groups/channels not allowed.

DigiByte Discussion

01 July 2026 19:05

That confirms my reading is same as theres. Chain will hard fork at 23808000 no matter what.

DigiByte Discussion

01 July 2026 18:36

Should be noted this wallet causes a hard fork at 23808000 assuming i read code correct

DigiByte Discussion

01 July 2026 18:19

I didnt read full code but Jared's pr would cause all these blocks to be invalid

DigiByte Discussion

01 July 2026 17:20

Won't the .3 change make the grostel blocks invalid and thus abandon that chain?

DigiByte Discussion

01 July 2026 16:56

Coinomi, ledger, ownbit, trust. Any bip39 multi wallet with long record is probably good.


The one you posted even if legit could be hacked and you not know

DigiByte Discussion

01 July 2026 16:53

I definetly would not trust it.

[Response to Post with link to possible fraud removed.]

DigiByte Discussion

01 July 2026 16:31

Hello ser 😁

DigiByte's wiki page is getting lots of traction right now and we would love to have a short research interview with anyone from the team.

Please is anyone from the team available for this?
Your time would be greatly appreciated 🙏

DigiByte Discussion

01 July 2026 11:55

Just type your questions/comments here. Do not DM people.

DigiByte Discussion

01 July 2026 10:15

Good morning.
Everything seems fine with this new version of the wallet (9.26.3), and it updated without any issues. Thank you very much. My question is: do I still need to modify the .conf file with
server=1
txindex=1
digidollar=1
under [main]?
Thanks again.

DigiByte Discussion

01 July 2026 08:04

Please join DigiByte Price & Speculations 💭🔮📈📉 for price talk.

DigiByte Discussion

01 July 2026 03:00

User Tineke Molenaar has 1/3 warnings; be careful!
Reason:
Promotion of other groups/channels not allowed.

DigiByte Discussion

30 June 2026 23:09

"Because DigiByte is being developed and supported by a Core-team and Community (all non-paid volunteers), we can never commit to dates to accomplish future projects.
Therefore, please consider future projects to be flexible in time.

Currently, DigiByte Core version 8.22 is being worked on, which has had significant improvements and optimizations implemented already. You can follow the updates, if you have a Github account, by navigating to the DigiByte Core repository and clicking the "Watch" button, and you will receive updates over email.

Furthermore, you can follow development discussions on our DigiByte Community Discord and Gitter."

DigiByte Discussion

30 June 2026 21:04

This is from the 9.26.2 release notes, the first is node configuration, the second is for mining / pools. I’m not a miner but if you read the notes and find the answer to your question please share here and in the mining channel.

DigiByte Discussion

30 June 2026 20:26

just started, syncing from scratch

DigiByte Discussion

01 July 2026 23:32

https://youtu.be/2z0TrP2aHAk?is=zmbbEH-jqP-g9fNl

DigiByte Discussion

01 July 2026 19:02

This is from the release notes but I’m sure you can verify by looking at v9.26.3

DigiByte Discussion

01 July 2026 18:28

Never mind. They added a cheat so it will work up to block 23808000.

DigiByte Discussion

01 July 2026 17:22

The .3 fixes the syncing issue, there are still 6 mining algos. In the message Jared shared legit miners/pools are out working the rouge miner.

DigiByte Discussion

01 July 2026 17:04

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 Discussion

01 July 2026 16:54

Which wallet do you recommend?

DigiByte Discussion

01 July 2026 16:32

What are your questions?

DigiByte Discussion

01 July 2026 16:04

Hi, Roald. If your question is still relevant, you can test our pool(sha256d only), fully compatible with v9.26.3

https://bitcoincashpool.org/dgb/


minunim difficulty is 2048

stratum+tcp://eu.bitcoincashpool.org:3333

dgb1walletaddress.worker

We need to hit at least 1 valid block to prove that we are ok with the network changes.

DigiByte Discussion

01 July 2026 11:55

Yes, leave those there if you want to enable DigiDollar when it activates.

DigiByte Discussion

01 July 2026 08:28

I thought I'd see something like this released 🙂

DigiByte Discussion

01 July 2026 04:48

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

DigiByte Discussion

01 July 2026 02:15

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.2 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.2.

DigiByte Discussion

30 June 2026 23:09

📢 Announcement – Great News! 🚀

New coins are now available for mining on Bitsolo.me

• BCH – Bitcoin Cash
• DGB – DigiByte 🔥🔥🔥
• MYT – Mytherra
• BCH2 – Bitcoin Cash 2

Start mining now and enjoy! 💪⛏️

DigiByte Discussion

30 June 2026 20:54

is digidollar=1 mandatory in a config for mining purposes?

DigiByte Discussion

30 June 2026 20:26

Resync completely. Delete the old blocks and start fresh