BitcoinDesign / Guide

A free, open-source community resource for designers, developers and others working on non-custodial bitcoin products.
https://bitcoin.design/guide/
Other
455 stars 98 forks source link

Explore and document how to handle send fees #997

Closed steynviljoen67 closed 1 year ago

steynviljoen67 commented 1 year ago

Describe your content request

When a customer sends bitcoin to another wallet, fees can be included within the amount you want to send or on top of the amount. There are some slight nuances that creates a bad experience.

This request is to explore and document what the different alternatives are.

Link to the page Still to be determined

Why would you like to change the content? We currently don't have this documentation in our guides

Suggestions No suggestions yet

Additional context This request came up in the General channel: https://bitcoindesign.slack.com/archives/C014J9ZKXB4/p1678778610650009

yashrajd commented 1 year ago

@steynviljoen67 An example of service provider(s) fees that we discussed: https://twitter.com/bitcoinkeeper_/status/1634953589620891648

These would factor into the considerations for our scenarios.

steynviljoen67 commented 1 year ago

Great, thank you!

On 10 Apr 2023, at 16:31, yashrajd @.***> wrote:

@steynviljoen67 https://github.com/steynviljoen67 An example of service provider(s) fees that we discussed: https://twitter.com/bitcoinkeeper_/status/1634953589620891648

These would factor into the considerations for our scenarios.

— Reply to this email directly, view it on GitHub https://github.com/BitcoinDesign/Guide/issues/997#issuecomment-1501888975, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZ5MPIGLGZGYY4PXWHTSPEDXAQKSLANCNFSM6AAAAAAWBDRLJU. You are receiving this because you were mentioned.

mouxdesign commented 1 year ago

Adding the draft

GBKS commented 1 year ago

@yashrajd did you meant to post your comment on issue #989? Seems more relevant there.

GBKS commented 1 year ago

Just took a look at the document. I think it's a good time to design screen mock-ups for this, you can probably communicate a good part of the content visually.

steynviljoen67 commented 1 year ago

Cool, I'll put some screens together and circulate for feedback.

GBKS commented 1 year ago

Quick update on this issue. @steynviljoen67 is pretty swamped right now so I'll help wrap things up. After reviewing all the work done, I'd recommend that we extract the Fees section in the Daily spending wallet -> Sending page into a separate sub-page. There's already a good amount of information there that we can add Steyn's research to. That will give us a dedicated page for anything related to fees, both onchain and lightning. This is more convenient for readers, and allows us to dive into more detail and edge cases because we have the dedicated space. I'll bring that up in the jam session today and if everyone's OK with it, set up a PR. How does that sound, Steyn?

steynviljoen67 commented 1 year ago

Thanks Christoph, that makes sense to me. Thanks for picking it up for me. 🙏🏻

On Mon, 03 Jul 2023 at 13:13, Christoph Ono @.***> wrote:

Quick update on this issue. @steynviljoen67 https://github.com/steynviljoen67 is pretty swamped right now so I'll help wrap things up. After reviewing all the work done, I'd recommend that we extract the Fees section https://bitcoin.design/guide/daily-spending-wallet/sending/#fees in the Daily spending wallet -> Sending page into a separate sub-page. There's already a good amount of information there that we can add Steyn's research to. That will give us a dedicated page for anything related to fees, both onchain and lightning. This is more convenient for readers, and allows us to dive into more detail and edge cases because we have the dedicated space. I'll bring that up in the jam session today and if everyone's OK with it, set up a PR. How does that sound, Steyn?

— Reply to this email directly, view it on GitHub https://github.com/BitcoinDesign/Guide/issues/997#issuecomment-1617975765, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZ5MPIDH7NYGFWOJLSAYC5LXOKSOVANCNFSM6AAAAAAWBDRLJU . You are receiving this because you were mentioned.Message ID: @.***>

GBKS commented 1 year ago

@steynviljoen67 I just created a pull request with my proposal for adding your research, married with the content we already have. Please take a look and let me know what you think.