← index

/btcwire:0.5.0/hemi-soak:1.0/ annoucing its address on many ports (82.221.101.217)

An archive of bnoc.xyz · view original topic →

· stratospher · #1 ·

I found it hard to believe the number of IP addresses received including duplicates rose to 460,241 addresses on 31 august in a node I was looking at.

Apparently 99.2% of all the addresses which got rate limited in net_processing in the node’s debug.log (since it started) came from 1 ip address 82.221.101.217 which advertises it’s own IP addresses on 67 different ports. It sends all addresses with services = 0, so none of them would enter the addrman anyways.

I tried connecting to it:

side note: this isn’t responsible for the recent increase in KIT’s Unique Addresses per Day graph after mid-august since the graph doesn’t count duplicates.

· stratospher · #2 ·

hmm probably software on some other chain accidentally connecting to us? seeing this on bitnod.es. seems to have connected to other normal nodes as well.

EDIT: no idea and could 100% be wrong but maybe https://hemi.xyz

· Jonathan Harvey-Buschel · #3 · · in reply to #2

I couldn’t find that specific UA string in their repo, but it is referenced here:

And that project is definitely using btcd & related deps. in a few places, for light clients and/or full nodes of some sort.

· stratospher · #4 · · in reply to #3

oh wow, thanks for finding that UA! currently seeing 4,298,947 addresses from that IP address which got rate limited. maybe we should open an issue there.

EDIT: created an issue

· stratospher · #5 · · in reply to #4


we checked @b10c’s peer-observer graphs and saw this IP disconnecting on 20 sep ~21:18 UTC across many nodes. :headstone: :blossom: