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.

Sign up for GitHub

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

Jump to bottom

Implement limits per user, sybil protection (IP, address, PoW, etc.) at a sentry level #21

Closed
1 of 2 tasks
Ivshti opened this issue Jan 4, 2019 · 1 comment · Fixed by #131
Closed
1 of 2 tasks

Implement limits per user, sybil protection (IP, address, PoW, etc.) at a sentry level #21

Ivshti opened this issue Jan 4, 2019 · 1 comment · Fixed by #131
Milestone
v0.5

Comments

@Ivshti
Copy link
Member

Ivshti commented Jan 4, 2019 •
edited
Loading

in the best case we can do everything through an NGINX config

initial limit ideas:

  • event submissions per (channel, publisher) per IP
  • event subimssions per (channel, publisher) per solved memory-bound PoW (Cuckoo Cycle?)
@Ivshti Ivshti added this to the release-1 milestone Jan 4, 2019
@samparsky
Copy link
Contributor

samparsky commented Jan 19, 2019 •
edited
Loading

@Ivshti Handling this through NGINX would be much preferable, as it reduces processing from the application layer.
Openresty is very suitable for this

@Ivshti Ivshti changed the title Implement limits per user (IP, address, PoW, etc.) at a sentry level Implement limits per user, sybil protection (IP, address, PoW, etc.) at a sentry level Jan 28, 2019
@Ivshti Ivshti modified the milestones: release-1, release-1.5 Mar 13, 2019
@Ivshti Ivshti mentioned this issue Apr 19, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v0.5
Development

Successfully merging a pull request may close this issue.

enhancement: eventSubmission AmbireTech/adex-validator
2 participants
@Ivshti @samparsky