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
At the time of sending, I went in to "Advanced", and set the "Fee Rate" at 6 sat/B given that fees were extremely low at the time. I noticed that the total fee estimate shown on the top of that page didn't seem to go any lower than the value corresponding to 10 sat/B, but I figured this is likely a display bug, and that the real fee would be set to the level I have specifically chosen on this page.
However, the transaction did indeed send at 10 sat! And of course given the network conditions at that time, it got confirmed faster than one can blink an eye. So I actually lost some funds as a result of this arbitrary fee decision by the wallet.
I should point out that I have my wallet set to sync directly with the blockchain ("slow" sync), and it did sync completely before I sent the transaction.
This is a critical bug that must be prioritized and fixed immediately.
The text was updated successfully, but these errors were encountered:
At the time of sending, I went in to "Advanced", and set the "Fee Rate" at 6 sat/B given that fees were extremely low at the time. I noticed that the total fee estimate shown on the top of that page didn't seem to go any lower than the value corresponding to 10 sat/B, but I figured this is likely a display bug, and that the real fee would be set to the level I have specifically chosen on this page.
However, the transaction did indeed send at 10 sat! And of course given the network conditions at that time, it got confirmed faster than one can blink an eye. So I actually lost some funds as a result of this arbitrary fee decision by the wallet.
I should point out that I have my wallet set to sync directly with the blockchain ("slow" sync), and it did sync completely before I sent the transaction.
This is a critical bug that must be prioritized and fixed immediately.
The text was updated successfully, but these errors were encountered: