-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Issues submitting proposal with less than 7.46 BSQ available #2613
Comments
In case the tx would create a dust output (e.g. 3 BSQQ input - 2 BSQ fee -> 1 BSQ) the tx is not allowed. |
Great thanks btw for finding such non trivial bugs! |
I could reproduce it but I did not get an invalid tx. |
Tried a few times but never got an invalid tx. Can you email me the log file? |
Ah now I see the invalid tx... will check... |
Ah the invalid tx happens when it was exactly 2 BSQ! Good find that would have been a critical bug! |
Fixes bisq-network#2613 If the user has the exact fee in his wallet no BSQ change output would be created but that violates our requirement for compensation or reimbursement txs. Beside that the error message for dust outputs was not clear.
@devinbileck I think that finding justifies a bug bounty payment. I would estimate it with 1000 BSQ. |
We could create a bug trophy hall somewhere, with the advertised bounties. |
When attempting to create a compensation request with exactly 2 BSQ in my wallet, the compensation request is submitted without error but upon generating the next block, the transaction gets marked as invalid.
To reproduce, using regtest, I sent 10 BSQ to a new wallet and then sent 8 back so I had only 2 BSQ (to work around the minimum dust limit). I then submitted a compensation request.
The following was in the log:
I then repeated the process of transferring BSQ to ensure I only had exactly 3 BSQ and this time I was unable to submit the compensation request:
This above error occurred until I had at least 8 (I assume more accurately 7.46) BSQ available at which point submitting a compensation request was successful.
So we need to prevent the invalid transaction in the first case (exactly 2 BSQ), and improve the error in the other case (less than 7.46 BSQ).
The text was updated successfully, but these errors were encountered: