You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 10, 2023. It is now read-only.
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
I've added a new versioned "feature", FEATURES.SAFE_TX_GAS_OPTIONAL.
If we detect a 1.3.0 Safe, don't request safeTxGas from backend, and don't show it in the UI.
NB: when we migrate to the /chains endpoint, the FEATURES logic will have to be refactored.
When the tx is created the SafeTxGas still has a value != 0 and it can be edited. There is no reason for that, we could force to be = 0 and a non editable input (or if it is possible to hide the input here it and still send the 0 when the tx is created/executed works as well)
This is the creation of a tx of a safe with a policy of 2 or more owners
I missunderstood the ticket. I thought that 1.3.0 were not passing the parameter at all and other versions were passing a fixed 0 for safeTxGas.
Ok, the ticket is fine then:
Safes 1.3.0 are not showing the input and passing a 0 as SafeTxGas
Safes < 1.3.0 are showing the safeTxGas as normal then.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
4 participants
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 #2878
How this PR fixes it
I've added a new versioned "feature",
FEATURES.SAFE_TX_GAS_OPTIONAL
.If we detect a 1.3.0 Safe, don't request safeTxGas from backend, and don't show it in the UI.
NB: when we migrate to the
/chains
endpoint, the FEATURES logic will have to be refactored.How to test it
Screenshots
Look ma, no safeTxGas!