-
Notifications
You must be signed in to change notification settings - Fork 91
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
Add snapshot user registry #709
Conversation
* @dev Reject user | ||
* @param _user user account address | ||
*/ | ||
function rejectUser(address _user) external onlyOwner { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are the purposes of rejectUser
and resetUser
?
How do we envision them being used in practice, @yuetloo?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking to let the coordinator reject sybil accounts. But, you're right that in practice, it's too late as once the user is added, they would've contributed and in the round.
} | ||
}) | ||
|
||
describe('Add user', function () { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be good to add tests for users that currently meet the requirements, but did not at the snapshot block, and for users who do not currently meet the requirements, but did at the snapshot block.
Closing this PR as changes have been merged to #711 |
This user registry will add users who can be verified by the proof of token ownership at a snapshot block.