-
Notifications
You must be signed in to change notification settings - Fork 778
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
[feature request] Simplify display of confirmations #679
Comments
i like the idea. so the whole section probably needs a slight redesign. having something visual to show the confirmations (maybe in form of a clock that fills up like in bitcoinQT) would sure be nice. however, we shouldnt start working on this before having at least some draft of how things should look like. if its worth it or if the overall redesign of the whole application should be pushed, that needs to be discussed. removing blockheight probably wont be possible, since the main sorting is happening there (and the timestamp cant be used) |
Yeah, this would be great.
Good point. But why can't the timestamp be used? |
becasue timestamps are set by the miners and can be slightly off: also its much easier to test, since the same default sorting applies in the CLI wallet. also, we just had issues with the sorting in the past and just chose the easy route due to time pressure: mbg033#70 |
+feature |
Thanks for explaining @medusadigital... strange that times they can be so far off. |
The history page looks like this now: @jonathancross Do you consider this resolved? |
Yes, thanks! |
After a transaction receives the suggested 10 confirmations, the user is not left with a clear sense that this is now safe / complete.
It would be nice to see a checkmark (or another visual indicator) marking the tx as "confirmed" with the actual number of confirmations added to the "Transaction Details" modal along with "BlockHeight". Could optionally show the number of confirmations on mouseover.
This would allow us to reduce the noise on the main list by removing "BlockHeight".
Thoughts?
The text was updated successfully, but these errors were encountered: