4 ms·
This helps some I guess, but I don't think it'd be that hard to take out all or almost all of the hardcoded initialization nodes if they're able to get IRC take
by cookiecaper 16y ago
This helps some I guess, but I don't think it'd be that hard to take out all or almost all of the hardcoded initialization nodes if they're able to get IRC taken down, too. btc really needs a more robust method to locate peers. IRC with a few hardcoded fallback nodes is not very decentralized imo.
- mike_esspe 16y agoHardcoded nodes are only needed if that's your first start. After that bitcoin client collects a databases of nodes, listening to "addr" messages from the network. On the next restarts, it uses addresses from that database one by one. And there are about 300 hardcoded nodes right now from different countries.
- cookiecaper 16y agoI see. That's better I suppose. You just need a relatively easy way to update the seed nodes in case all of the included nodes are down. Does this exist? If not, maybe I'll add it to the client.
- mike_esspe 16y agoThere is a dns-seeding (currently two domains which respond with multiple A records, pointing to known good nodes). I think hardcoded nodes are updated only manually via git.