-
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
Accepted offer failed to execute, went through anyway but never happened. #2112
Comments
trade state now being in 'TAKER_FEE_PUBLISHED' , can i just continue then? this interface could really get a 'history' tab ... |
retried later , made sure i had -more- inside wallet then needed, instead of exact amount, and didnt hit the same error, trade executed well |
@buzztiaan Seems a bug caused that the reserved funds for the trade got released incorrectly. Have u updated to 0.9? If not tomorrow is a new release, please update, there are many bug fixes. If you have more problems like that please check out https://bisq.community/t/how-to-switch-to-a-new-data-directory/6753/ |
If you lost the trade fee you can request reimbursement here: https://github.com/bisq-network/support/issues/ |
i used 0.9 , it seems the bug has to do with one of these msgs; WARN b.c.b.w.BisqRiskAnalysis: TX considered non-standard due to unknown version number 2 either that, or it was just the fact that my bisq wallet held exactly what i needed for the transactions, no extras |
@oscarguindzberg - do you think it can be related to the "version number 2" issue? |
Posting "version number 2" bug here for clarity #1832.
My first guess is the InsufficientMoneyException is caused by the bisq wallet having exactly the amount it has to send (0.011xxx) and then being unable to pay the tx fee (aka miner fee) of the funding tx. |
@ManfredKarrer Should this issue still be kept open? |
@ripcurlx Maybe it is related to the other issue with InsufficientMoneyException? |
@ManfredKarrer Yes, could be. I'll have to dig deeper into the trading process anyways because of #2305. Let's see if I find something suspicious on the way. |
i accepted a offer, funded the bisq wallet from external wallet, funded the offer from bisq wallet, and then:
while the actual TX that bisq sent for the trade offer acceptance actually -did- have a 0.011xxx BTC output.
later on restarting numerous times i get the 0.011xxx back in wallet and log file messages like
Dec-11 19:24:34.433 [JavaFX Application Thread] WARN b.core.offer.OpenOfferManager: We found an outdated addressEntry for openOffer RSExxx-xxx-xx-x-x-x-x
The text was updated successfully, but these errors were encountered: