SYBILing nodes! 😱 Exploiting IC Network... Community Attention Required!

Wonder what the future holds when ICP discussion starts talking about filabustering/rejecting major proposals just cuz :thinking:

I guess ICP yield through proof of vote is good… and we can also force deflation via proof of burn.

And when Dfinity loses the votes maybe icp can get more deflation with proof of reject, :rofl:

When you get sybil attack via NNS votes, I guess the backstop would be node collusion to prevent it. :rofl:

1 Like

Hey @alexu, out of interest where does your tooling locate this Blockchain Development Labs node? → Node Machine: 2h6dm-k5h3n-nmqek-m5gty-yy3xq-a3atf-54its-biy25-ijh3c-xvit4-mae - ICP Dashboard

The IC registry seems to think it’s in a completely different location and country than censys (which uses ipinfo.io and is generally very accurate, using a probe network for request/response latency analysis).

2001:438:8000:10:6801:1cff:fe00:e4aa - Host Summary - Censys

Here’s the discrepancy illustrated.

1 Like

Hi @Lorimer !

The world-wide ping for this node confirms its location in North America. A localized 1ms ping reply from a probe in Toronto strongly suggests the node is within 100km radius of that location. I hope this helps! :slight_smile:

4 Likes

Thanks! First time I’ve seen censys coming up short. I’ll turn to RIPE Atlas next time :slightly_smiling_face:

1 Like