Forked chain #415

Activity

1. 8eS3rz4sDu8oUx4q39hhv8o2k2e72dkb commented on Jun 30, 2026

   

   8eS3rz4sDu8oUx4q39hhv8o2k2e72dkb

   on Jun 30, 2026

   Last edited by 8eS3rz4sDu8oUx4q39hhv8o2k2e72dkb

   More actions

   1)Upgrade asap to v.9.26.2 and fully rescan your blockchain. (it is better to completely remove the /blocks, /chainstate, /indexes folders from .digibyte directory)

   2)Add these nodes and keys to the config for fast sync:

   reindex=1 (then change it to 0)
   dbcache=8192
   maxmempool=512
   blockonly=1 (then change it to 0 or comment with a '#' after initial blocks download)
   addnode=134.56.44.241
   addnode=135.181.130.229
   addnode=15.164.205.209
   addnode=162.55.88.217
   addnode=167.235.35.169
   addnode=172.104.191.6
   addnode=174.131.163.123
   addnode=18.179.157.124
   addnode=2.25.204.180
   addnode=24.101.86.120
   addnode=3.113.201.20
   addnode=37.59.32.10
   addnode=38.74.44.120
   addnode=47.91.28.96
   addnode=54.229.85.145
   addnode=64.182.71.11
   addnode=64.182.71.16
   addnode=64.182.71.26
   addnode=64.182.71.56
   addnode=71.54.200.164
   addnode=73.11.190.77
   addnode=8.209.234.102
   addnode=80.122.131.94
   addnode=80.42.227.233
   addnode=84.30.137.73
   addnode=88.116.128.130
   addnode=88.117.161.226
   addnode=88.117.242.238
   addnode=oracle1.digibyte.io:12024
   addnode=digihash.digibyte.io:12024
   addnode=digiexplorer.info:12024
2. JaredTate commented on Jun 30, 2026

   

   JaredTate

   on Jun 30, 2026

   More actions

   This issue will be fixed shortly in v9.26.3, all sync issues will be fixed: #417
3. JaredTate commented on Jun 30, 2026

   

   JaredTate

   on Jun 30, 2026

   More actions

   If you are having issues syncing DigiByte v9.26.2 make your digibyte.conf in the default $DGB data directory look like this:

   [main]
   server=1
   listen=1
   txindex=1
   digidollar=1
   minimumchainwork=00
   
   addnode=oracle1.digibyte.io:12024
   addnode=digihash.digibyte.io:12024
   addnode=digiexplorer.info:12024
   

   There was an incorrect minimumchainwork setting added in v9.26.2 release that will be fixed shortly with v9.26.3.

   We manually confirmed adding 'minimumchainwork=00' to digibyte.conf fixes sync issue, it was not peers, it was not v7 nodes on wrong chain.

   The issue was minimumchainwork was added in BTC v25 and does not apply to DGB multialgo.

   We calculated a recent block 23.5 million chain work for v9.26.2 and it only adds up to 28% in pre-sync and resets because the check is not properly adapted to DGB multi algo.

   So we return to same default setting for what we had in v7 and v8.
4. ycagel

   closed this as completedon Aug 8, 2026