Deprecate zkSync #1004
Merged
Deprecate zkSync #1004
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mmv08
approved these changes
Jun 27, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now that zkSync Era has a full EVM compatibility layer, this PR deprecates EraVM Safe deployments (in order to reduce maintenance burden and only release a single set of contract byte code instead of two).
Starting with version 1.5.0, we will no longer officially support deploying EraVM versions of the Safe contracts.
Note however, that EraVM contracts cannot
DELEGATECALLinto EVM contracts, meaning that existing EraVM Safe proxies cannot be upgraded to EVM versions. Legacy accounts should either remain on an older version of Safe (<= v1.4.1), or migrate the account to a new EVM version.