-
Notifications
You must be signed in to change notification settings - Fork 477
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reference transaction trusted
flag when showing the UnsignedWarning
#1220
Comments
Shouldn't we use only the trusted flag? |
Yes, |
@francovenica the trusted flag is now on the staging backend, please test the following cases: The fix is on dev (https://safe-web-core.dev.5afe.dev/).
|
I just created an unsigned transaction on staging here for you to confirm: |
Adding this scenario affecting safe apps: untrusted.mp4When the pop up to view the transaction is clicked, txs are showing as untrusted for me until the transaction is indexed. Then it will lose this status. |
@JagoFigueroa fixed in #1261. Immediately executed transactions in 1/x Safes won't be visible until executed. |
What is the feature about
The
UnsignedWarning
is currently shown when no signatures are present. However, the gateway will soon forward thetrusted
flag of each transaction as well, which should also be referenced.The list of requirements
The conditional rendering logic needs to be extend to include the
trusted
flag as follows:Links
The text was updated successfully, but these errors were encountered: