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

Stuck transaction even post-arbitrator cancellation. #3335

Closed
ifarnung opened this issue Sep 27, 2019 · 6 comments
Closed

Stuck transaction even post-arbitrator cancellation. #3335

ifarnung opened this issue Sep 27, 2019 · 6 comments

Comments

@ifarnung
Copy link

image
This transaction that never confirmed on the blockchain and was eventually handled and cancelled by an arbitrator, is still sitting pending in my 'Funds' log.

How to resolve this?

  1. What happened to that .003 BTC that was being sent for security deposit? I guess it never left the UTXO set that I control? But will BISQ software see that UTXO as spent or available?
  2. The fact that I have this pending unconfirmed transaction is making my mining fee estimates higher across all my future BISQ orders, and I haven't replaced any trading orders since this happened because I am waiting for a fix.

This is the final communication from the arbitrator.
image

@wiz
Copy link
Contributor

wiz commented Sep 27, 2019

Try settings -> network info -> delete spv file and resync

@ifarnung
Copy link
Author

That worked perfect, thanks. The .003 is back in my Avail Balance and the pending transaction is gone from the history. I wonder if I saw it was stuck within the first hour of that trade trying and failing to confirm, had I reset the SPV, could that have gotten the trade to go correctly? Not sure, but anyway, closing this issue. Thanks @wiz

@huey735
Copy link
Contributor

huey735 commented Sep 27, 2019

Related to #3306

@huey735
Copy link
Contributor

huey735 commented Sep 27, 2019

I wonder if I saw it was stuck within the first hour of that trade trying and failing to confirm, had I reset the SPV, could that have gotten the trade to go correctly?

That's a good question, @ifarnung. @sqrrm @ManfredKarrer will the resync of the SPV cause problems to open trades?

@wiz
Copy link
Contributor

wiz commented Oct 1, 2019

hey @ifarnung do you remember if you set custom fees to 1 sat/byte in your settings at the time this bug occurred? there seems to be 2 bugs causing TX fail to broadcast, one for "dust" and one for "fee too low", but the latter would only occur if you set fees to 1 sat/byte because default is 10 sats/byte minimum so just want to get more information to help investigation thanks

@ifarnung
Copy link
Author

ifarnung commented Oct 1, 2019

No I did not set it so low, maybe 5 or 6 sats was the lowest I used.

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

4 participants