Transaction decoding v1: design decisions

Links 1 - Owners don’t know what they’re signing 📆

Mobile Show decoded function & params on tx details v1 #329 🐱 Data decoding v2 - Special handling for multisends #350 🐱 Data decoding v3 - More info in Multisends #351 🐱 Data decoding v2 and v3 - Special handling for multisends 📆 Multisend Miro board 📌

Web Transaction context #244 🐱 Transaction context #338 🐱

Decoding Transaction Information in Tx List #882 🐱 Decode multiSend tx details #1106 🐱 Add "Action" details in transaction list #1134 🐱

Platform: mobile, web

App version: Android 2.2.0, web v2.9.0

Which problem do we solve? Owners don’t know what they’re signing (see 1 - Owners don’t know what they’re signing). Transaction data is cryptic.

How does the feature fit into the product and larger product decisions? This feature changes the way data is displayed in contract interactions and custom transactions. Before we displayed hex data without decoding (on mobile - with amount of bytes):