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
Would like to see some more information on the "transaction successfully sent" page. For example:
Time/Date
Total Amount Sent
Total Fees in sat and % of total amount sent (so people know how awesome lightning is).
Invoice memo
Total hops needed to route the payment. Total paths needed to route the payment.
Time required to route the payment.
Most of this information is available (except for the % fee) in the transactions/activity history, but we shouldn't have to navigate around to get there, and #1328 is a major barrier.
The text was updated successfully, but these errors were encountered:
I understand the demand for some details, but since space is rare on the phone, I think we should keep it short. As you pointed out, all details are available via Activity already (meanwhile we also have % fee). The only thing Zeus doesn't display here is, how long a payment took. Also, when you see the success screen, everything happened just now, so for example you can simply move your eyes up a few cm and see the time on your phone :D But of course I get it, it is kind of convenient to have all the information summed up for your.
I think displaying Amount with Fee (e.g. 1 021 sats + 1 sat fee (~0.1%)) would be nice, since user cannot know the fee before payment went through. Total amount of hops, which hops were used, elapsed time for payment etc. is definitely advanced information, which should not be displayed by default.
What about having a "Payment Details" button on the success screen which sends you to the payment details view (same as tapping a payment in Activity)?
Describe the feature
Would like to see some more information on the "transaction successfully sent" page. For example:
Most of this information is available (except for the % fee) in the transactions/activity history, but we shouldn't have to navigate around to get there, and #1328 is a major barrier.
The text was updated successfully, but these errors were encountered: