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

create emergency stop/pause button #2

Open
nopslip opened this issue Apr 2, 2021 · 0 comments
Open

create emergency stop/pause button #2

nopslip opened this issue Apr 2, 2021 · 0 comments

Comments

@nopslip
Copy link
Owner

nopslip commented Apr 2, 2021

Monitor token claims closely. Assuming we do implement check on user_id : amount ratio we will shrink attack vector on fraudulent/malicious token claims down to a valid user_id : amount ratio. Thus, we should monitor claims from the same address closely. Also, from the same source IP web2/quad-lands side fwiw.

In the event that we spot suspicious claims (successful claim source address > 3?) or some other suspicious condition is observed we will want to have a clean/easy/efficient way to pause the signed message server.

On pause we will want/need to make sure that quadlands is informed and behaves in a predictable user friendly way. "The airdrop is currently paused. After maintenance is complete, the drop will taken live again" or whatever.

Should pause kill whole app or just prevent signed claims? This depends on if we think the signing server itself is compromised I guess.

https://github.com/nopslip/gitcoin-web-ql/issues/149

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

No branches or pull requests

1 participant