stackingsaunter
commented
2 months ago So I think there are two scenarios at play now and two ways we can do this:
1. We seperate payment requests from transaction details
- payment requests display multiple transactions ("activity") to the same address
- transaction detail pages then just display one transaction
2. We "merge" payment requests with transaction details, when transaction is noticed by mempool.
- So in that case payment request dissapears in the UI and is effectively a state of transaction before it is noticed by Core. - - We loose viewing payment requests history in that case though I think.
Transactions and payment requests can be linked together, and addresses can be used multiple times. If addresses are re-used, this linking may get a bit messy. For example, you received two transactions on an address for which you created one payment request. How can and should the UI display that?
This will likely be an addition to the transaction details screen covered in the activity page in the design docs.