This repository has been archived by the owner on Nov 10, 2023. It is now read-only.
fix: transaction stage-relative execution #3323
Merged
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
Resolves #3305
How this PR fixes it
Instead of blanket establishing
isExecution
withinTxSender
, the logic is now extracted into the respective transaction creation/processing function as the previous logic was before the refactor.On top of this, the transaction proposal to backend now depends on whether the user is an owner.
How to test it
Every variation of transaction is affected by this. The cases are as follows:
1/? threshold:
2+/? threshold:
Safe creation