Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

Add explanation for why the fee is unknown when sending a LN payment #2676

Closed
bolatovumar opened this issue Aug 2, 2019 · 3 comments · Fixed by #3528
Closed

Add explanation for why the fee is unknown when sending a LN payment #2676

bolatovumar opened this issue Aug 2, 2019 · 3 comments · Fixed by #3528
Assignees
Labels
scope: ui/ux issues with user interface or user experience in general type: enhancement New feature or request
Milestone

Comments

@bolatovumar
Copy link
Contributor

I wonder if it would be useful to add an explanation for why the fee is unknown when sending an LN payment.

Screen Shot 2019-08-02 at 3 45 13 PM

Context

Seeing an "unknown" fee could confuse some people and make them wonder if they are going to overpay in fees.

Possible Implementation

Use the tooltip component with an explanation like in the "Receive Bitcoin" screen (see screenshot below)
Screen Shot 2019-08-02 at 3 47 19 PM

Your Environment

  • Zap version: 0.5.2-beta
@JimmyMow
Copy link
Member

JimmyMow commented Aug 7, 2019

@bolatovumar hmmm, the only reason you would see this is because you don't have enough funds I think? Maybe the error in the bottom should be more apparent to the user? Either way, nice suggestion this makes sense to me

@bolatovumar
Copy link
Contributor Author

@JimmyMow I mean specifically about the "Fee unknown" row in the "Send Bitcoins" table. As I understand we do not know the exact fee ahead of time because your payment may be routed through nodes which can have different routing fees, right? In any case the fee is probably going to be very small. This type of explanation in a tooltip could help those new to Lightning. Else it feels weird to send a payment with an "unknown" fee.

@mrfelton
Copy link
Member

mrfelton commented Aug 7, 2019

Unknown will show if queryRoutes failed to return a potential route for any reason. This often indicates that the payment is likely to fail since there are no known routes, although this may not always be the case.

@mrfelton mrfelton added scope: ui/ux issues with user interface or user experience in general type: enhancement New feature or request labels May 24, 2020
@mrfelton mrfelton added this to the v0.7.0-beta milestone May 24, 2020
@mrfelton mrfelton self-assigned this May 24, 2020
mrfelton added a commit to mrfelton/zap-desktop that referenced this issue May 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
scope: ui/ux issues with user interface or user experience in general type: enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants