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

Limit rewards per IPv4 /24 subnet #29

Closed
3 tasks done
Tracked by #46
bajtos opened this issue Oct 3, 2023 · 4 comments
Closed
3 tasks done
Tracked by #46

Limit rewards per IPv4 /24 subnet #29

bajtos opened this issue Oct 3, 2023 · 4 comments
Assignees

Comments

@bajtos
Copy link
Member

bajtos commented Oct 3, 2023

When calculating SPARK rewards, we can see many nodes completing the same task. To make sybil attacks more expensive, we should reward only one checker in each IPv4 /24 subnet.

Tasks

Preview Give feedback
@bajtos
Copy link
Member Author

bajtos commented Oct 16, 2023

The grouping algorithm must allow us to identify participants from U.S- or E.U.- sanctioned countries to implement geofencing and ensure we don't pay them.

@patrickwoodhead
Copy link

Cloudflare using IPV6 which is slowing things down a bit.

@bajtos
Copy link
Member Author

bajtos commented Oct 24, 2023

The grouping algorithm must allow us to identify participants from U.S- or E.U.- sanctioned countries to implement geofencing and ensure we don't pay them.

We decided to implement a different solution: we put Cloudflare's WAF (web application firewall) in front of SPARK API and configured it to reject requests coming from the sanctioned countries.

@bajtos bajtos closed this as completed Nov 2, 2023
@github-project-automation github-project-automation bot moved this from 🏗 in progress to ✅ done in Space Meridian Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ done
Development

No branches or pull requests

2 participants