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
In the transaction confirmation flow, there should be no address/hash shortening applied but instead, the full content displayed. This is especially relevant for To fields, safeTx hashes, domain and message hashes etc. If we run into UX issues due to the length of some hashes, we could consider prioritizing certain fields.
The list of requirements
check design implications of overall removal of tx shortening in the tx confirmation
optional: prioritize certain fields
Designs/sketches
tbd
Links
The text was updated successfully, but these errors were encountered:
What is the feature about
In the transaction confirmation flow, there should be no address/hash shortening applied but instead, the full content displayed. This is especially relevant for To fields, safeTx hashes, domain and message hashes etc. If we run into UX issues due to the length of some hashes, we could consider prioritizing certain fields.
The list of requirements
Designs/sketches
Links
The text was updated successfully, but these errors were encountered: