Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DGB Seed Nodes Update #66

Merged
merged 1 commit into from
Aug 22, 2021

Conversation

JaredTate
Copy link

@JaredTate JaredTate commented Aug 20, 2021

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

@gto90 gto90 requested review from SmartArray, gto90 and a team August 20, 2021 21:47
Copy link

@SmartArray SmartArray left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK

@Quakeitup
Copy link

dgb.quakeguy.com

@ycagel ycagel merged commit 725707a into DigiByte-Core:feature/8.22.0 Aug 22, 2021
@ycagel
Copy link
Member

ycagel commented Aug 22, 2021

cACK

@wiria
Copy link

wiria commented Aug 23, 2021

dgb.nul.io

@barrystyle
Copy link

Had issues resolving the following few entries;

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

@ChillingSilence
Copy link

ChillingSilence commented Aug 29, 2021

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
Copy link

@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:/DigiByte-Core/digibyte-seeder

@Quakeitup
Copy link

Quakeitup commented Feb 9, 2023 via email

@saltedlolly
Copy link

@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
Copy link

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
Copy link

@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
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants