Allow Safe delegates to propose transactions #209
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
|
CLA Assistant Lite All Contributors have signed the CLA. |
iamacook
approved these changes
Jun 17, 2022
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.
What it solves
This PR allows Safe delegates to propose Safe transactions using the Safe Service Client.
How this PR fixes it
The
proposeTransactionmethod was refactored to accept the signature of the sender (owner or delegate) instead of getting the signature from thesafeTransactionobject passed to that same method (that only contains signatures from owners).In addition, the check that only allowed Safe owners to call the
signTransactionHashmethod in the Safe Core SDK was removed to allow Safe delegates to generate the signature.