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

cdk-erigon: Fetch burn address & GER data when we have access to the chain #565

Closed
LindaGuiga opened this issue Aug 29, 2024 · 1 comment
Labels
crate: zero_bin Anything related to the zero-bin subcrates.

Comments

@LindaGuiga
Copy link
Contributor

#463 introduces the concept of burn addresses, where the fees to be burnt are stored, so they can later be burnt on L1. This is used in cdk-erigon. But since we do not yet have access to the cdk-erigon chain, the burn_address that is currently set in zero-bin is the default address (0x00...0). Once we can, we should actually retrieve the correct burn address from the chain instead.

@github-project-automation github-project-automation bot moved this to Backlog in Zero EVM Aug 29, 2024
@Nashtare Nashtare added the crate: zero_bin Anything related to the zero-bin subcrates. label Aug 29, 2024
@Nashtare Nashtare added this to the Type 2 - Q3 2024 milestone Aug 29, 2024
@Nashtare Nashtare moved this from Backlog to Todo in Zero EVM Sep 6, 2024
@Nashtare Nashtare changed the title cdk-erigon: Fetch the actual burn address when we have access to the chain cdk-erigon: Fetch burn address & GER data when we have access to the chain Sep 17, 2024
@Nashtare
Copy link
Collaborator

Expanding the notion to burn address and GER data, post #594

@github-project-automation github-project-automation bot moved this from Todo to Done in Zero EVM Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
crate: zero_bin Anything related to the zero-bin subcrates.
Projects
Status: Done
Development

No branches or pull requests

2 participants