Milestone 1.5: Activity - specs & progress

[GBKS]

This is a tracker/discssion issue for the 1.5 milestone (design docs).

Goal is to add transaction handling and display. So far, the application can only create and manage wallets, but there is no balance or transaction list. That's what we add here.

Additions:

• Activity screen
• Transaction details
• Balance display

Questions:

• What other activities should be in the activity list? Transactions and...? Will we eventually have things like key rotation, backup reminders, or otherwise?
• Do we want to offer search and filter options for the activity list?
• What are all the transaction states we need to offer? This would be great to have a spec'd list.

Some cleaned-up designs from last years explorations:

[GBKS]

We also need a state for indicating when transactions are still being verified, more here (related to assumeUTXO). This does not necessarily have to be an indicator on each transaction, it could also be a more general message, or even just something that shows up when trying to send UTXOs that have not been verified yet.

[GBKS]

Another state to address is when received coins are time-locked. This was brought up in this podcast episode.

There is a bit of a chicken-end-egg situation. If the application does not let you create time-locks, then why display them. Well, you might be able to create them in a separate wallet. Displaying is also a lighter load development-wise than creating. So we could start with the display side, and the create side would be part of #65 anyways.

[GBKS]

In the design call #92, we talked about potentially showing payment requests in activity. Logic is that a payment request gets completed by an incoming transaction. We'll explore this in the 1.6 milestone.

[GBKS]

The design docs for activity were just updated via this PR.

I noted a few outstanding to-dos on that page and will repeat them here:

• Fee bump interaction flow
• Cancel transaction flow
• Indicator for address re-use
• Clarify how payment request info is shown on the transaction page
• Mock-up various transaction states, to show color and shape coding