Set default Safe version to 1.3.0 #484
Merged
Conversation
This file contains 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
germartinez
requested review from
dasanra,
yagopv and
DaniSomoza
and removed request for
dasanra
DaniSomoza
approved these changes
Jul 13, 2023
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.
The SDK supports the Safe Contracts
v1.4.1, but because they are only deployed in a couple of networks, we will still have thev1.3.0as default.In case developers want to deploy
v1.4.1Safes, they will need to pass thesafeVersionproperty with value1.4.1in the initialization of theSafeFactoryclass in theprotocol-kit. Existingv1.4.1Safes are compatible by default with no specific setups.