Bitcoind protects against this by storing the addresses it has learned
about in buckets. The bucket an address is stored in is chosen based on the
IP of the peer that advertised the addr message, and the address in the
addr message itself. The idea is that the bucketing is done in a randomized
way
Also (I am fuzzy on the details for this), Bitcoind will detect when a node
is misbehaving and (I believe) it will blacklist misbehaving nodes for a
period of time so it doesn't continually keep trying to connect to tarpit
nodes, for example.
On Wed, Mar 4, 2015 at 6:13 PM, Kevin Greene
Hi, so just a thought as my node relays addresses etc. If I wanted to really
slow down communication over the P2P network, what's stopping me from popping
up a heap of dummy nodes that do nothing more than exchange version and relay
addresses, except I send addr messages with all 1000
Interesting!
Thanks Kevin, I now need to research this and include such protections in my
node.
Also (I am fuzzy on the details for this), Bitcoind will detect when a node is
misbehaving and (I believe) it will blacklist misbehaving nodes for a period of
time so it doesn't continually keep
4 matches
Mail list logo
