Trade stuck at 'Wait for blockchain confirmation'


#1

I’m new to bisq and unsure if I’m just being impatient. I took an offer around 12 hours ago to sell BTC for GRC. The transaction is still pending on the ‘wait for blockchain confirmation’ step. The maker fee is visible on bitaps, but neither the taker fee nor deposit are to be seen.

Maker fee ID: 4a7c299e512f46889cebb8c542a3b3f228ca2ce6b4f80541e53c0e29c0fadde4
Taker fee ID: ff370d9263265fa3e56e202bd6d42812f2e1ff3111d8a9e43ae5c9b4806b4a12
Deposit ID: 947ef0e951009b5b3f82cea13d7af40ae6b7de5cae74c819f31a9671e0c835bc


#2

It seems like your transactions didn’t get published for some reason.
Maybe try deleting the SPV chain file in Settings.


#3

I deleted the SVP file via the button in settings. The app resynced and then restarted. When I go back to the open trade the taker fee is unconfirmed and now I cannot see the deposit ID.

Roughly what should my expectation be for getting past the first step? It’s essentially 3 bitcoin transactions that have to be confirmed… which may take 10 minutes to a couple hours? Is that correct?


#4

No, there seems to be an issue with your client publishing the transactions to the network.
I am not sure why this is the case. Maybe a faulty connection to the Tor network or to Bitcoin nodes.

This trade hasn’t really started and you haven’t payed the trading fee yet, as transactions never happened on the blockchain. You should still have access to your funds in case you want to withdraw them using emergency wallet tool by pressing cmd+e.


#5

Indeed, the funds show simultaneously as ‘Locked in trades’ and ‘Available as balance’. I was able to open a trade offer using these funds without using the emergency wallet tool.

I don’t think I have a faulty connection to Bisq peers, as I can see traffic flowing over the connected peers on the onion addresses. How do you recommend verifying connectivity to the bitcoin network? Should I try to connect to the Bitcoin network w/o using Tor (if I do not mind relinquishing some privacy)? I am currently configured to ‘Use Tor for Bitcoin network’ and ‘Use provided Bitcoin Core nodes’.

One more data point is that when I create offers I am able to successfully post my maker fee transaction onto the Bitcoin network. The failure to post to the network only appears to have occurred on the one offer I took.


#6

Then it might just be a problem with that offer in particular.
I don’t really know of any easy way to check your connection, maybe looking at logs for any errors is best you could do.

If you don’t mind losing some privacy, you could use a public Bitcoin network instead of provided nodes, but you should probably do this only if you keep experiencing this issue.

I am glad that you were able to use your funds without much additional effort :slight_smile:


#7

I only see 1 WARN around the time of the transactions.

Mar-23 07:21:32.272 [JavaFX Application Thread] WARN i.b.c.b.w.Broadcaster: Broadcast of tx 947ef0e951009b5b3f82cea13d7af40ae6b7de5cae74c819f31a9671e0c835bc not completed after 8 sec. We optimistically assume that the tx broadcast succeeded and call onSuccess on the callback handler.

There are other INFO lines that make it seem as though the taker fee transaction was processed successfully:

Mar-23 07:21:32.272 [JavaFX Application Thread] INFO o.b.w.Wallet: marked ff370d9263265fa3e56e202bd6d42812f2e1ff3111d8a9e43ae5c9b4806b4a12:1 as spent by 947ef0e951009b5b3f82cea13d7af40ae6b7de5cae74c819f31a9671e0c835bc

Let me know if there are specific log lines that would be helpful for me to share. If you believe this could be an issue in the bisq application, then I am happy to provide what ever information is required to troubleshoot and/or open an issue on the repo.


#8

There is also a lot of noise in the logs currently as a result of the hanging/unprocessed transaction:

Mar-24 16:02:30.907 [JavaFX Application Thread] WARN i.b.c.t.Trade: depositTx is null
Mar-24 16:02:30.907 [JavaFX Application Thread] WARN i.b.c.t.Trade: depositTx is null
Mar-24 16:02:30.907 [JavaFX Application Thread] WARN i.b.c.t.Trade: depositTx is null
Mar-24 16:02:30.907 [JavaFX Application Thread] WARN i.b.c.t.Trade: depositTx is null
Mar-24 16:02:30.907 [JavaFX Application Thread] WARN i.b.c.t.Trade: depositTx is null
Mar-24 16:02:30.907 [JavaFX Application Thread] WARN i.b.c.t.Trade: depositTx is null
Mar-24 16:02:30.907 [JavaFX Application Thread] WARN i.b.c.t.Trade: depositTx is null
Mar-24 16:02:30.907 [JavaFX Application Thread] WARN i.b.c.t.Trade: depositTx is null
Mar-24 16:02:30.907 [JavaFX Application Thread] WARN i.b.c.t.Trade: depositTx is null
Mar-24 16:02:30.907 [JavaFX Application Thread] WARN i.b.c.t.Trade: depositTx is null


#9

@kevinjos and I are picking this up in arbitration now. Sorry you had this experience your first time out with Bisq. Failed trades like this do occur from time to time, but they are the exception.


#10

Thanks for cleaning up the state @cbeams. Please let me know if there’s anything I can do to help troubleshoot what went wrong. My interest is in learning from the experience and helping improve the software if possible.


#11

I experienced the same false start on my second ever trade. In this case I was the maker. Could this be an issue with my setup (bisq/machine/firewall)? Or is it simply a bad stroke of luck running into the same transient bug twice?


#12

Maybe there is something wrong with your Tor circuits. I don’t know if deleting old Tor data in Settings would mess with your open offers.
Maybe you should try it when you have no open offers or trades anymore and report back whether this helped with your issue.


#13

i have the same problem.
its just hanging with no confirmations.

i had the same issue with a withdrawl days ago which is still hanging with my coin stuck/lost.
not good