-
Notifications
You must be signed in to change notification settings - Fork 11
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
ReimbursementPool on Lynx #323
Conversation
Contract deployed in Amoy: https://amoy.polygonscan.com/address/0x53fe19093be1ac0136d33d91e01aba4aa381b87b |
/// with this reimbursment pool. Can be unauthorized by the | ||
/// owner only. | ||
/// @param _contract Authorized contract. | ||
function unauthorize(address _contract) 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.
Bit of a nitpick. I know this was copied from a Keep contract, but should this be deauthorize
? We've used the authorize/deauthorize
parlance in other areas.
Same comment for the event.
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 agree that there's a divergence wrt to staking contracts but this contract is not related to staking, and I'd prefer if we limit changes unless we really need them.
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.
Definitely not a "need" 😄
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.
🎸
Type of PR:
Required reviews:
What this does:
ReimbursementPool
on CoordinatorIssues fixed/closed:
Why it's needed:
Notes for reviewers: