This repository has been archived by the owner on Nov 10, 2023. It is now read-only.
fix: remove unnecessary transaction proposals #3328
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 #3326
How this PR fixes it
Transaction proposal now takes whether the transaction is being immediately created and executed into account. Proposals now only occur when a transaction is being created, created and immediately executed (1 threshold) or confirmed. (Execution should not propose).
An extra flag is now passed from
processTransaction
to ourTxSender
:approveAndExecute
. This flag is referenced to determineisImmediateExecution
(a 1/? threshold Safe creating and immediately execution a transaction):How to test it
Please bear in mind that this touches upon all transaction types.
All reference data cases in the issue HAVE been successfully tested, but it should also be verified on hardware wallets.
There should be NO backend proposal network call when executing the following