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

[WIP] Support Celo native's credit and debit gas fee functions #3162

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

martinvol
Copy link

@martinvol martinvol commented Jul 3, 2023

  • 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

@martinvol martinvol changed the title Support Celo native's credit and debit gas fee functions [WIP] Support Celo native's credit and debit gas fee functions Jul 3, 2023
/**
* @notice Reverts for non-Celo chains
*/
modifier onlyCeloChains() {
Copy link
Collaborator

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.

Copy link
Collaborator

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 🤔

Copy link
Contributor

@gator-boi gator-boi left a 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.

@martinvol
Copy link
Author

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.

@evan-gray evan-gray added the evm label Mar 14, 2024
@SEJeff
Copy link
Collaborator

SEJeff commented Apr 26, 2024

@martinvol do you still want to work on this?

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

Successfully merging this pull request may close these issues.

None yet

4 participants