Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Estimate the cost of controlling a majority of SPARK checker network #31

Open
Tracked by #46 ...
bajtos opened this issue Oct 3, 2023 · 1 comment
Open
Tracked by #46 ...

Comments

@bajtos
Copy link
Member

bajtos commented Oct 3, 2023

Assuming we implement the planned fraud-countering steps (#29, #30, space-meridian/roadmap#41):

How much would it cost for a single party to launch a Sybil attack on our network, gain control of the majority of the nodes (or results reported) and thus be able to submit fake retrieval measurements that will be considered as real?

@bajtos
Copy link
Member Author

bajtos commented Oct 12, 2023

Few comments on using IPv4 as a scarce resource:

Folks running the IPFS DHT learned that this approach is not effective against an attacker willing to pay, well, just about anything. Unfortunately, there are quite a few "residential VPN" services that'll let you get as many IP addresses as you want for almost nothing (usually used for spam, crime, etc.).

This is the core diversity logic in the IPFS DHT: go-libp2p-kbucket/peerdiversity/filter.go
Instead of just looking at IPs, they map them to known ASNs and try to achieve ASN diversity. But even that fails if an attacker is willing to use a residential VPN and/or a botnet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🗃 backlog
Development

No branches or pull requests

1 participant