So I’m the BTC buyer as maker. Someone accepted my offer and sent the taker fee. In the block explorers I can see his transaction already has over 50 confirmations. But Bisq itself doesn’t show a check mark next to the transaction id with the “Confirmed in xxx block(s)” tooltip, like it does for my maker fee tx.
Now I don’t know if something is going wrong with my Bisq, or if the check mark just isn’t supposed to be shown for the taker fee transaction. Should I be worried?
If restarting the app doesn’t work, try deleting the SPV chain file in Settings and restarting the app.
I reset the spvchain and let it resync. There’s still no check mark next to the taker fee transaction ID. The confirmation count in the maker fee tx ID tooltip is correct, so the blockchain does seem to be synced…
Can you open a dispute with cmd+o?
No, I can’t. Whenever I press Alt+O and click “Open support ticket”, the following lines are printed to the log file:
Okt-12 16:08:42.740 [JavaFX Application Thread] INFO b.d.m.p.p.PendingTradesDataModel: Trade.depositTx is null. We try to find the tx in our wallet.
Okt-12 16:08:42.740 [JavaFX Application Thread] ERROR b.d.m.p.p.PendingTradesDataModel: Trade.depositTx is null and we did not find any MultiSig transaction.
Other than that, nothing happens.
Additional log file observations:
My client asked the seller’s client to publish the deposit transaction:
Okt-12 04:43:53.507 [JavaFX Application Thread] INFO b.c.t.p.t.m.MakerSendPublishDepositTxRequest: Send PublishDepositTxRequest to peer kjo76akha4xi6j6j.onion:9999. tradeId=YfhmuL-5f68b757-4fea-4a6d-b6e8-59df60829377-080, uid=caa26c6d-2ebf-42ba-86db-6030dc113f9d
Okt-12 04:43:53.551 [JavaFX Application Thread] INFO b.c.t.p.t.m.MakerSendPublishDepositTxRequest: PublishDepositTxRequest arrived at peer kjo76akha4xi6j6j.onion:9999. tradeId=YfhmuL-5f68b757-4fea-4a6d-b6e8-59df60829377-080, uid=caa26c6d-2ebf-42ba-86db-6030dc113f9d
Okt-12 04:43:53.551 [JavaFX Application Thread] INFO b.c.trade.Trade: Set new state at BuyerAsMakerTrade (id=YfhmuL): MAKER_SAW_ARRIVED_PUBLISH_DEPOSIT_TX_REQUEST
Okt-12 04:43:53.552 [JavaFX Application Thread] INFO b.c.t.p.TradeProtocol: Send AckMessage for PayDepositRequest to peer kjo76akha4xi6j6j.onion:9999. tradeId=YfhmuL-5f68b757-4fea-4a6d-b6e8-59df60829377-080, sourceUid=7958e07f-9c60-4477-857d-47387c603cdf
Okt-12 04:43:53.564 [JavaFX Application Thread] INFO b.c.t.p.TradeProtocol: AckMessage for PayDepositRequest arrived at peer kjo76akha4xi6j6j.onion:9999. tradeId=YfhmuL-5f68b757-4fea-4a6d-b6e8-59df60829377-080, sourceUid=7958e07f-9c60-4477-857d-47387c603cdf
2 minutes later, the connection to the seller timed out:
Okt-12 04:45:53.488 [InputHandler-kjo76akha4xi6j6j.onion:9999] INFO b.n.p.n.Connection$SharedModel: Shut down caused by exception java.net.SocketTimeoutException: Read timed out on connection=Connection{peerAddress=Optional[kjo76akha4xi6j6j.onion:9999], peerType=DIRECT_MSG_PEER, uid='e7943103-bb17-4c09-a6ae-5c2cf97a826d'}
Okt-12 04:45:53.488 [JavaFX Application Thread] INFO b.n.p.p.PeerManager: onDisconnect called: nodeAddress=Optional[kjo76akha4xi6j6j.onion:9999], closeConnectionReason=CloseConnectionReason{sendCloseMessage=false, isIntended=false} SOCKET_TIMEOUT
Okt-12 04:45:53.488 [JavaFX Application Thread] INFO b.n.p.p.p.PeerExchangeManager: onDisconnect closeConnectionReason=CloseConnectionReason{sendCloseMessage=false, isIntended=false} SOCKET_TIMEOUT, nodeAddressOpt=Optional[kjo76akha4xi6j6j.onion:9999]
By searching for the multisig address in the prepared deposit transaction on a block explorer, I can confirm that the deposit transaction was never published to the blockchain.
So does this mean something went wrong on the seller’s side?
The number of timeouts on the network (mainly Tor) is higher than usual today.
Your seller sendings may unfortunately have been concerned.