-
Notifications
You must be signed in to change notification settings - Fork 0
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
DevouchAttester with multiAttest Support & Fee Recollection #8
base: master
Are you sure you want to change the base?
Conversation
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.
please dm me once comments are resolved. Thanks
|
||
emit Log("attested", gasleft()); | ||
function updateEAS(address newEASAddress) public ownerOnly { | ||
eas = IEAS(newEASAddress); |
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.
will EAS Address for a chain change frequently ? If no, why do we need it as a variable?
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.
my thought was about uncertainty in the future, it's unlikely but it could happen. We can remove it if you want anyway - I don't think it matters that much on gas costs
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.
to make an unchanging value as a variable we also add the getter / setter methods. So its better to keep it as a constant for now.
src/DevouchAttester.sol
Outdated
(bool success, ) = multisig.call{value: address(this).balance}(""); | ||
require(success, "Failed to send Ether"); | ||
emit Log("withdraw", gasleft()); | ||
function withdraw() public ownerOnly { |
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.
anyone in GM should be able to withdraw. We have ensured that no matter who withdraws , the money always goes to multisig.
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.
This is Griff's requirement
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.
@jainkrati @mateodaza is there also a ownerOnly function to change the target recipient then? In case we need to change which multisig receives the funds. Apologies if it's already in the code somewhere
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.
nope, good catch - will add it 👍🏼
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 trust you will take care of the last comment. Approving.
excellent @mateodaza is this ready for a merge then? |
No description provided.