DGB Seed Nodes Update

[JaredTate]

Signed-off-by: Jared Tate [email protected]

After looking through the hardcoded seed nodes for DigiByte-Core as well as digibytewallet-core for the mobile wallets both codebases need to be updated with more seeds to help fix connection issues now being experienced, especially the light wallets.

Running a DGB core seed node is simple. You just need to have a URL (example: seed.digibyte.io) and a DigiByte Core full node of the latest version that's running 24/7 at that address. It's also helpful to add "maxconnections=800" or any higher number to allow more than 8 peers at a time in the digibyte.conf file.

If you are interested in running a full-time seed node for the next few years to help the network out please mention it in a comment below with the URL. Let me know if you see any issues with seeds listed below.

        //DigiByte Community Seed Nodes
        vSeeds.emplace_back("seed.digibyte.org"); // Website collective
        vSeeds.emplace_back("seed.digibyte.io"); // Jared Tate
        vSeeds.emplace_back("seed.digihash.co"); // Jared Tate
        vSeeds.emplace_back("dnsseed.esotericizm.site"); // DigiContributor
        vSeeds.emplace_back("seed.digibytefoundation.org"); // DigiByte Foundation
        vSeeds.emplace_back("seed.digiexplorer.info"); // DigiByte Foundation
        vSeeds.emplace_back("seed.digiassets.net"); // DigiByte Foundation
        vSeeds.emplace_back("digibyteblockexplorer.com"); // DigiByte Block Explorer
        vSeeds.emplace_back("dgb1.trezor.io"); // Trezor
        vSeeds.emplace_back("seed2.digibyte.io"); // Jared Tate
        vSeeds.emplace_back("seed3.digibyte.io"); // Jared Tate
        vSeeds.emplace_back("seed.digibyteblockchain.com"); // JS555
        vSeeds.emplace_back("seed.digibyte.host"); // SashaD
        vSeeds.emplace_back("seed.digibyteservers.io"); // ChillingSilence

[SmartArray]

ACK

[Quakeitup]

dgb.quakeguy.com

[ycagel]

cACK

[wiria]

dgb.nul.io

[barrystyle]

Had issues resolving the following few entries;

dnsseed.esotericizm.site
seed.digibytefoundation.org
seed.digibyteblockchain.com

[ChillingSilence]

It's more than that. It's not just that some are failing to resolve at a DNS level, but in addition many in the list are not dnsseeds, and checks on UDP 53 need to be done. This should not have been merged.

ONLY:

seed.digibyte.org
seed.digibyte.io
seed.digibyteservers.io

are correctly responding when checked with nslookup for example.

To my knowledge this list has absolutely nothing whatsoever to do with maxconnections, nor the node itself running on TCP port 12024.

[saltedlolly]

@Quakeitup I see you are running a full node at dgb.quakeguy.com

Would you be willing to also run a DigiByte Seeder alongside your full node?

We need a few more DigiByte Seeders: https://github.com/DigiByte-Core/digibyte-seeder

[Quakeitup]

Yes of course. I'll need to migrate to better "hardware" first. It's been a plan to move the node to a faster system for a while but this gives me the push I needed. I'll add seed node that to the plan. If I had to give an ETA I'd say online by March 1st. Thanks, Quakeitup

…

On Thu, Feb 9, 2023, 7:43 AM Olly Stedall ***@***.***> wrote: @Quakeitup <https://github.com/Quakeitup> I see you are running a full node at dgb.quakeguy.com Would you be willing to also run a DigiByte Seeder alongside your full node? We need a few more DigiByte Seeders: https://github.com/DigiByte-Core/digibyte-seeder — Reply to this email directly, view it on GitHub <#66 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGVUKYFK6ZONV5FWSEKYZLWWTQ73ANCNFSM5CRCNPYA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[saltedlolly]

@Quakeitup That's great to hear. It's worth mentioning that the resources required to run a DiiByte Seeder are very low - it is simply a lightweight DNS server so if you are already running a full node, then running a Seeder as well should be easy. I have written up a full tutorial here.

We are also encouraging people to provide their name and contact info if they are running a seeder, given what an important piece of infrastructure it is. This way it is easy to contact them in the event of a problem. Details are in the document I have linked to.

[saltedlolly]

Can anyone tell me who manages seed.digibyte.org? It just says "Website Collective". It would be good to have a contact person for this. Is it @makyurt?

[saltedlolly]

@wiria You previously ran a DigiByte Node, but I don't see it any more. It would be really beneficial to have a DigiByte Seeder in Asia. Is this something you could help with? As you can see with the new seeder list, we are well covered in the US, but it would be nice to have Seeders in Asia and Europe: https://1drv.ms/w/s!AsTGLNLt5YBypgadXSi16NEPaXes

[saltedlolly]

Does anyone know who owns digibytefoundation.org ? It is hardcoded into v7.17.3 and says "DigiByte Foundation". Rudy tells me they do not own that domain - they use digibytefoundation.io only. Rudy thinks it may be owned by @JaredTate or possibly Josiah?