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

Support devchain with L2 already transitioned #11103

Closed
Tracked by #10990
martinvol opened this issue Jul 1, 2024 · 5 comments · Fixed by #11107
Closed
Tracked by #10990

Support devchain with L2 already transitioned #11103

martinvol opened this issue Jul 1, 2024 · 5 comments · Fixed by #11107
Assignees

Comments

@martinvol
Copy link
Contributor

martinvol commented Jul 1, 2024

Currently the devchain is created with latest contracts in the commit it is built. The devtooling team ready wants to start working on celi/contractkit changes that require an L2 enabled.

It could be acheived by, after the job that builds L1 (current one) finishes, applying a second set of migrations that:

  1. import the state into a new anvil version.
  2. Sets the bytecode of proxyAdminAddress (0x4200000000000000000000000000000000000018) (this enables the transition)
  3. Calls functions to fully enable the contract (for example CeloDistributionSchedule.activate(...))
  4. Exports a new state that it's L2.
@arthurgousset
Copy link
Contributor

Extra context from Slack

@arthurgousset
Copy link
Contributor

Starting to work on this today.

@arthurgousset
Copy link
Contributor

Marked the PR ready for review:

@arthurgousset
Copy link
Contributor

@arthurgousset
Copy link
Contributor

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

Successfully merging a pull request may close this issue.

2 participants