-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add transaction details to transactions in wallet history #872
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Note; #1054 partially addresses this but some more modelling work is required to show everything in the detail requested here |
With reference to the 'fee' row in the lightning payment example - is it not the case that lightning fees are per-channel and not per-transaction? |
You are paying fees for outgoing transactions. The amount of fees is defined through the route (channels) you are using. |
Ah, I see, thanks! So they are 'per-channel' insofar as the channel defines the fee, but the fee is paid upon every payment too? |
Do we want to model other timestamps than just the time we 'first learned' about this payment? E.g invoice creation timestamp |
With #1213, we will model all information required to fulfill this ticket. Now, onto prettifying it as per the Figma :) I will start on that tomorrow! 🎉 |
Nit on figma: "you sent -1000" sats would imply that you received 1000 sats, wouldn't it? Maybe we can convey this in a different way? |
Thought: we could have outgoing transactions have red amount text and incoming have green? |
Upon clicking a transaction one should see some details to the transaction. There are different types of transactions for which a details view is required.
Figma mock:
https://www.figma.com/file/Sr3SfZ46sZstKjSwftmTtc/10101-v1-(incl-bitcoin.design)?type=design&node-id=7375%3A45885&mode=design&t=tFOk1Qr2JvlNIaBY-1
E.g. like this
Screen.Recording.2023-08-04.at.3.05.02.pm.mov
The text was updated successfully, but these errors were encountered: