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

Deterministic Deployment: altering opcodes for specific chains #4749

Open
ryestew opened this issue Apr 22, 2024 · 0 comments
Open

Deterministic Deployment: altering opcodes for specific chains #4749

ryestew opened this issue Apr 22, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request
Projects

Comments

@ryestew
Copy link
Collaborator

ryestew commented Apr 22, 2024

Coogan from ZKSync was musing about the possibility of tweaking opcodes for helping deploy to different L2 chains. We should investigate the possibilities of how this can be done, who is doing anything like this, and what are the risks. OpenZeppelin Defender does do deterministic deployment. This does seem more than deploying the same contract to different chains but getting the same address - like our contract deployer does.

@ryestew ryestew added the enhancement New feature or request label Apr 22, 2024
@ryestew ryestew added this to Needs triage in Backlog via automation Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Backlog
  
Needs triage
Development

No branches or pull requests

2 participants