Leaving the issue at hand aside, I thought this was a good insight into how bitcoin core nodes find peers on the network (using a hardcoded list of seed nodes)
Also new to me was the list of requirements for running a dns seed node.
pull down to refresh
Leaving the issue at hand aside, I thought this was a good insight into how bitcoin core nodes find peers on the network (using a hardcoded list of seed nodes)
Also new to me was the list of requirements for running a dns seed node.
Not quite correct: that's the first method they try. But if that fails, there is a backup list of IP addresses that are tried too. Also, for Tor only nodes, IIRC there's some fixed
.onionaddresses that are tried too. I2P probably has something similar.If you run a node with
-connect, the seed nodes and other mechanisms aren't used. Similarly, if you use-addnode, provided your node works and returns addresses, the seed nodes aren't that relevant either.Assuming your ISP isn't themselves MITM attacking you, you only need a single "honest" peer for Bitcoin to properly connect to the P2P network. So the seed node mechanism has a lot of redundancy.
BTW, the reason why DNS is used in the first place is because DNS is heavily cached at multiple levels. That makes it extremely difficult for the people running the DNS seeds to:
This protects users by making it very difficult to use DNS seeds to attack people.
wow thanks for the great insight Peter!
Yes, there are hardcoded list of both
.onionand.i2ppeers too, updated from time to time. https://github.com/bitcoin/bitcoin/tree/master/contrib/seedsRunning
onionANDi2pwould help here even if ISP is trying to MITM attack you.This guy is so annoying
They're developing a coinjoin protocol on nostr (yay?) but my God their Twitter is cancerous to look at. Always mad about something
He's been working on it for years and last I looked it could be easily ddosed
who ? the PR troll ?
They all need to touch some grass
I learned about this mechanism when I asked ChatGPT about it a few months ago.
It can be overridden manually by editing bitcoin.conf, which you have to do anyway to connect over Tor only.
https://jlopp.github.io/bitcoin-core-config-generator/#config=eyJfX2ludGVybmFsIjp7InBsYXRmb3JtIjoiV2luZG93cyJ9fQ==
Bitcoin needs more software plurality.
There should be an alternative node implementation, independent from Bitcoin Core.
There should be more decentralised solutions for things like DNS lists or node IP/onion seed lists.
Spiral grantee Johannes Hofmann has also done good research work on this topic.
https://21.ninja/
view on www.youtube.comI didn't know it was like that. Thanks for sharing
Sometimes you don’t think it be like that, but it do.
deleted by author