-
Notifications
You must be signed in to change notification settings - Fork 652
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
[WIP] Support Celo native's credit and debit gas fee functions #3162
base: main
Are you sure you want to change the base?
Conversation
martinvol
commented
Jul 3, 2023
•
edited
edited
- Add modifier so that only vm can call
- Add modifier so that it can only be called on Celo (by checking Celo Registry address has bytecode)
- Add credit and debit functions
- Add Fundry tests
- Check with wormhole team how to refactor to comply with repo guidelines
/** | ||
* @notice Reverts for non-Celo chains | ||
*/ | ||
modifier onlyCeloChains() { |
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.
Perhaps we should use the Wormhole chain id here.
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.
Or maybe not because this is in the token 🤔
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.
A few of us have discussed how to include this change in the existing TokenImplementation
contract.
How do you feel about creating a second TokenImplementation
contract with the Celo-specific functionality that inherits from the existing contract? This way the Celo-specific code is not deployed to other blockchains when the TokenImplementation
contract is upgraded.
Yeah, makes sense. My original intention with this PR was to pull it in front of your team so you could suggest me the better course of action. Even if this code gets deployed only on Celo, I'd still include the checks to make sure the chain is actually Celo compatible. |
@martinvol do you still want to work on this? |