Fix: Update dnsseeds for mainnet / testnet#34
Merged
gto90 merged 2 commits intoDigiByte-Core:developfrom Apr 20, 2021
ChillingSilence:fix/dnsseed
Merged
Fix: Update dnsseeds for mainnet / testnet#34gto90 merged 2 commits intoDigiByte-Core:developfrom ChillingSilence:fix/dnsseed
gto90 merged 2 commits intoDigiByte-Core:developfrom
ChillingSilence:fix/dnsseed
Conversation
SmartArray
approved these changes
Apr 18, 2021
SmartArray
left a comment
SmartArray
left a comment
There was a problem hiding this comment.
It's awesome that we have those comments, in case something is wrong with one of those seeders.
ACK
| vSeeds.emplace_back("seed.digibyte.io"); // JaredTate | ||
| vSeeds.emplace_back("seed.digibyteblockchain.com"); // JS555 | ||
| vSeeds.emplace_back("dnsseed.esotericizm.site"); // DigiContributor | ||
| vSeeds.emplace_back("seed.digibytefoundation.org"); // DigiByteFoundation |
Author
There was a problem hiding this comment.
Yes, need to help them get the servers up this week
| vSeeds.emplace_back("seed.digibyte.org"); // Website collective | ||
| vSeeds.emplace_back("seed.digibyteservers.io"); // ChillingSilence | ||
| vSeeds.emplace_back("seed.digibyte.io"); // JaredTate | ||
| vSeeds.emplace_back("seed.digibyteblockchain.com"); // JS555 |
There was a problem hiding this comment.
seed.digibyte.io, seed.digiexplorer.info & seed.digibytefoundation.org should be left in. We can get peer seeder nodes on all those domains. Not sure who runs digibyteblockchain.com. Is not me.
chappjc
reviewed
Dec 10, 2022
Comment on lines
+414
to
+415
| vSeeds.emplace_back("seed.testnet-1.us.digibyteservers.io"); | ||
| vSeeds.emplace_back("seed.testnetexplorer.digibyteservers.io"); |
There was a problem hiding this comment.
These two do not resolve. Can testnet seeds be brought up?
JohnnyLawDGB
added a commit
to JohnnyLawDGB/digibyte
that referenced
this pull request
Apr 6, 2026
…igiByte-Core#34) estimatecollateral read system health from a static cache (GetSystemMetrics) that is only populated when ScanUTXOSet() runs inside getdigidollarstats or getprotectionstatus. If estimatecollateral ran first, the cache had totalDDSupply=0, causing the health check to hardcode systemHealth=0 (emergency) and apply a 2x DCA multiplier. This doubled the reported collateral requirement even when the system was healthy at 475-528%. The mint transaction builder uses the same path, so valid mints were rejected with "Insufficient funds for collateral and fees." Fix: read totalCollateral and totalDDSupply from the digidollar stats index (fast, already synced) or fall back to ScanUTXOSet(), matching the pattern getdigidollarstats and getprotectionstatus already use. Also change the totalDD==0 case from health=0 to health=30000 (max) since an empty system has nothing at risk. Tested on testnet21: estimatecollateral now returns health=510 / DCA=1x matching getdigidollarstats and getprotectionstatus. Tier-4 mint that previously required 134K DGB now correctly requires 67K and succeeds. Confirmed still present in RC29 (RH-36a fixed a different cache race). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update dnsseeds for mainnet / testnet
Due to all the DNS changes over the last 24 months, many of these are stale (Servers offline / domains expired etc) and need updating.
The servers for this will be running:
https://github.com/DigiByte-Core/digibyte-seeder
Will need a confirmation of NS records etc from those managing the DigiByte.org domain etc prior to commit approval, working with them now to ensure they've setup the DNS side correctly.