You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: