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

Display total fee estimate when choosing to fund trade with BTC or BSQ #5327

Closed
phinneaus opened this issue Mar 18, 2021 · 12 comments
Closed

Comments

@phinneaus
Copy link

phinneaus commented Mar 18, 2021

Description

When issuing a maker offer, user is presented with the option of funding the transaction with either BTC or BSQ. BSQ appears to be significantly cheaper, but this does not take into account that there is an extra input / output to the transaction, resulting in mining fees that can be significantly higher.

Suggest displaying the total estimated cost (trade fee + mining fee estimate) when selecting between BTC and BSQ.

paste

Here are the two steps when choosing BSQ:
Screenshot from 2021-03-18 16-22-34
Screenshot from 2021-03-18 16-23-30

And here are the two steps when choosing BTC:
Screenshot from 2021-03-18 16-22-16
Screenshot from 2021-03-18 16-22-55

Total estimated fees in USD: $14.14 for BTC, $21.38 for BSQ (51% higher)

Version

1.5.9

Steps to reproduce

  1. Create offer to buy
  2. Observe trade fee currency options between BTC and BSQ

Expected behaviour

In addition to trade fee, show mining fee so user can evaluate total cost of trade before committing.

Actual behaviour

Trade fee alone is displayed on the initial create offer screen, estimated mining fee is not shown until the next step for committing the offer.

@boring-cyborg
Copy link

boring-cyborg bot commented Mar 18, 2021

Thanks for opening your first issue here!

Be sure to follow the issue template. Your issue will be reviewed by a maintainer and labeled for further action.

@wallclockbuilder
Copy link
Contributor

wallclockbuilder commented Mar 18, 2021

What statistics are you using to arrive at the 80% higher probability? It'll be helpful if you can show a screenshot comparison, bsq vs btc.

@phinneaus
Copy link
Author

Thanks @wallclockbuilder - I got the 80% # from the thread in Keybase, that was lazy of me, I'm sorry.

I added a set of screenshots to the original description and updated that - in my trial it was just over 50% higher total fees to use BSQ.

Especially since a user might click "Don't Show Again" on the confirmation screen, I think it would be helpful to push the mining fee estimate forward to the initial screen with the toggle.

Let me know if you have any feedback on that, and thank you again!

@wallclockbuilder
Copy link
Contributor

wallclockbuilder commented Mar 18, 2021

$BSQ increased the mining fee by 89%.
Thats an extra 17,000 Satoshis =~$10 #satstackers would rather avoid.
|
|
Mining fees increased by $10
Mining fee paid when fees in BTC
from about $11
|
|
Mining fee paid when fees in BSQ
to about $21

@wallclockbuilder
Copy link
Contributor

The cause of all this is the tx size. The tx size in vBytes for a trade fee(e.g. $1) is bigger in BSQ than BTC because the bitcoin wallet has segwit implemented. BSQ does not. Which reflects in the higher mining fee.

This is will be fixed when Segwit is fully implemented for BSQ.
Part one has already been merged into the v1.6.0 release(https://github.com/bisq-network/bisq/releases/tag/v1.6.0)
BSQ Segwit has been scheduled for activation at bitcoin block height 680300, which is approx April 25th(about a month away).

@Aman-1412
Copy link

Part one has already been merged into the v1.6.0 release(https://github.com/bisq-network/bisq/releases/tag/v1.6.0)
BSQ Segwit has been scheduled for activation at bitcoin block height 680300, which is approx April 25th(about a month away).

Looks like the second part of the PR was merged 3 hours ago and will be part of 1.6.3 #5109

@ghost
Copy link

ghost commented Apr 29, 2021

image

@phinneaus
Copy link
Author

@jmacxx - are you indicating that it is almost never a good idea to fund with BSQ? As a new user I was fairly swayed by all the comments in the documentation about how significant the savings would be for using BSQ. If your graphic is indicative of the situation moving forward those statements should probably be softened or clarified.

@ghost
Copy link

ghost commented Apr 30, 2021

It depends on trade size - the chart above is an example for "small" offers. You have to consider the different dynamics of trade size and trading fee vs mining fee at different mempool rates. The BSQ trading fee is priced at 50% of BTC but for small offers the trading fee is negligible compared to the mining fee. If you were making an offer for 1 BTC the discount offered by using BSQ would be 50% making it worthwhile.

In defense of the documentation, a year ago mining fees were routinely 10 sats/vB and at that price point using BSQ does give an overall discount. It could and should be explained more detail so people don't feel they've been scammed, but there is a tendency to gloss over the technicalities for "better UX". Perhaps if the existing documentation had a link to a "more technical" explanation it would satisfy both sets of users.

@phinneaus
Copy link
Author

That makes sense. Just comes down to education and understanding. FWIW the fiat method I use to trade (Fiat -> BTC) has a fairly low daily max, so .01 BTC is about the biggest possible trade unless I went to cash / postal money order. Thanks for your feedback!

@stale
Copy link

stale bot commented Aug 21, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the was:dropped label Aug 21, 2021
@stale
Copy link

stale bot commented Sep 6, 2021

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.

@stale stale bot closed this as completed Sep 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants