Skip to content
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 deeper guidance on lightning fee controls #863

Open
Bosch-0 opened this issue Jul 6, 2022 · 2 comments
Open

Add deeper guidance on lightning fee controls #863

Bosch-0 opened this issue Jul 6, 2022 · 2 comments
Labels
Copy Task is about improving text. Daily spending wallet Referring to the Daily spending wallet reference design section.

Comments

@Bosch-0
Copy link
Collaborator

Bosch-0 commented Jul 6, 2022

Wallets like Phoenix and Breez have some extra settings when it comes to managing lightning fees such as setting a max amount you want to pay for a payment. We should incorporate some of the below content into the guide.

image

@GBKS
Copy link
Contributor

GBKS commented Jul 6, 2022

I like this idea. I've found there's a lack of transparency around fees. Certain other well-known wallets don't even let you see what the fees were for a payment and you have to figure it out by subtracting the invoice amount from what was actually deducted from your balance.

@GBKS GBKS added Copy Task is about improving text. Daily spending wallet Referring to the Daily spending wallet reference design section. labels Jul 6, 2022
@pavlenex
Copy link
Contributor

pavlenex commented Jul 6, 2022

Talked to quite a few people lately, and most of their confusion around the wallets was indeed fee transparency. "Why does this wallet charge sometimes X and sometimes Y, and why is Z wallet 3 times the fees than Q wallet?"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Copy Task is about improving text. Daily spending wallet Referring to the Daily spending wallet reference design section.
Projects
None yet
Development

No branches or pull requests

3 participants