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

Prevent negative suggested mining fee when burning BSQ for fees #5643

Merged
merged 1 commit into from Aug 6, 2021
Merged

Prevent negative suggested mining fee when burning BSQ for fees #5643

merged 1 commit into from Aug 6, 2021

Conversation

ghost
Copy link

@ghost ghost commented Jul 30, 2021

Problem: Negative mining fees could be shown in the make/take offer summary popup when BSQ is used for fees and the BTC sats value of the BSQ is greater than the calculated transaction fee.

Using BSQ to pay trade fees burns the BSQ effectively paying miners with those sats. A bug surfaced whereby negative mining fees could be displayed, giving a false/confusing impression to users. Note that this is a display issue only, there were no problems with the trading transactions themselves.

After this fix, the displayed mining fee cannot be negative.

image

Screenshot from 2021-07-29 21-34-53

In these examples the BSQ fee rate (Param.java) was artificially increased to 100 BSQ/BTC producing larger than usual BSQ fees and triggering the bug in order to validate the fix.

@ripcurlx ripcurlx requested a review from sqrrm August 1, 2021 18:49
Copy link
Member

@sqrrm sqrrm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

@sqrrm sqrrm merged commit 374e76a into bisq-network:master Aug 6, 2021
@ripcurlx ripcurlx added this to the v1.7.3 milestone Aug 16, 2021
@ghost ghost mentioned this pull request Aug 19, 2021
@ghost ghost deleted the prevent_negative_mining_display branch May 29, 2022 22:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants