It took me 5 minutes to write a script for that. There’s 309 unique IPv4 addresses in this era.
That’s hilarious. In the previous comment in this very same thread you said my writing about this involved a trivial level of insight and laughed off the use of the word “chainalytics”.
Now in this comment you’re hinting at that what I wrote about should be treated as “confidential”. Which is it?
Any SecOps or chainalytics hobbyist already has all these tools and scripts (e.g. developed for Kusama or other Substrate-based chain) ready to run - they don’t need anyone’s help. All info is on XX chain or otherwise available to hundreds of people out there, including adversaries.
The reason why I haven’t even started doing any real “chainalytics” is that, sadly, I’ve seen enough by simply looking in the Explorer - didn’t even need to do graph analysis or look at the nodes w/o on-chain ID (the ones with were brazen enough).
For whatever reason, I’ve put in the work and time and you did not. And now there’s info out there to (roughly) understand the extent of this problem, and fix it.
For the record, as I’ve maintained throughout this topic, it’s a growing problem, but not a big problem: we have several non-transparent multi-node validators with 5 or more nodes, and we have several centralized pools. Both can be easily be dealt with, if xx Network finds that necessary.
I’ll keep highlighting these problems.