Skip to content

ZEVM contracts naming PROTOCOL_ADDRESS identifier naming #481

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.

Sign up for GitHub

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

Jump to bottom
Open
kingpinXD opened this issue Mar 19, 2025 · 0 comments
Open

ZEVM contracts naming PROTOCOL_ADDRESS identifier naming #481

kingpinXD opened this issue Mar 19, 2025 · 0 comments
Labels
zevm Related to zevm smart contract module

Comments

@kingpinXD
Copy link

kingpinXD commented Mar 19, 2025 •
edited
Loading

We use
PROTOCOL_ADDRESS and FUNGIBLE_MODULE_ADDRESS are used interchangeably in the contracts.

  • Gateway : uses constant PROTOCOL_ADDRESS = 0x735b14BB79463307AAcBED86DAf3322B1e6226aB;

  • ZRC20,SystemContract uses constant FUNGIBLE_MODULE_ADDRESS = 0x735b14BB79463307AAcBED86DAf3322B1e6226aB;

We should choose an identifier and use it everywhere
@kingpinXD kingpinXD added the zevm Related to zevm smart contract module label Mar 19, 2025
@kingpinXD kingpinXD changed the title ZEVM contracts naming ZEVM contracts naming PROTOCOL_ADDRESS idetifier naming Mar 19, 2025
@kingpinXD kingpinXD changed the title ZEVM contracts naming PROTOCOL_ADDRESS idetifier naming ZEVM contracts naming PROTOCOL_ADDRESS identifier naming Mar 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
zevm Related to zevm smart contract module
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kingpinXD