Skip to content
This repository was archived by the owner on Jun 10, 2026. It is now read-only.

Known addresses: design decisions

Sasha Postnikova edited this page Jan 12, 2021 · 4 revisions

Links
Display human readable names for known addresses #337 🐱
Display human readable names for known addresses #1638 🐱
2020-11 Kickoff: Known addresses 📆
Hypothetical press release 📆
List of known contracts 📆
Spec: Human readable names for Known addresses 📆

Platform: web, mobile

App version: tbd.

Which problem do we solve?
See 1 - Owners don’t know what they’re signing 📆.

How does the feature fit into the product and larger product decisions?
This will change the appearance of addresses in transactions list, details and in address book.

What are the metrics and KPIs we will be measuring for this feature?
tbd

Is there user research or quantitative data informing decisions made here?
Data from discovery interviews Q1 2020 💡
Insights from discovery interviews Q1 2020 💡

Screens

1. Contract interaction (undecoded data)

Main design decisions

1. ...

...

2. ...

...

3. ...

...

User tests – insights, changes after user tests

tbd

Changes after release, metrics

tbd

Clone this wiki locally