Locked in trades: 0.088 BTC

KlausHirsch · March 9, 2018, 5:58am

On the 28th of January I sold BTC for USD (Maker) and the buyer (Taker) took the offer but didn’t pay.
A dispute was opened and the Arbitrator wrote “Buyer could not pay, due to bank trouble”. Ticket closed Feb 1, 2018 6:56:08 PM

But since then I have 0.088 BTC in “Locked funds” and it’s still shown in “Open Trades” and I have no idea how to resolve that.

Arbitrator: 3b7cft5k4ae6a236.onion:9999

Trade ID: yevb5inj-3745eeee-9390-4849-a20b-f8ebe8e016db-063

Maker fee transaction ID: 43d3bcac248d16bdac06131f7b41b43190db1d94a106b5ecd02ec6fd2fb04f0a

Taker fee transaction ID: d6159a3f407e6f6fa406512d250ce58a8e33ff31ee0b013ab55637a69738c3b2

Deposit fee transaction ID: 075087bf22cb5a273ecc8195063cf880faefc1810313bbf86caa932b004e1d76

cbeams · March 9, 2018, 7:20am

Re-syncing your SPV file should do the trick. Settings->Network info->Delete SPV file and resync.

KlausHirsch · March 12, 2018, 3:57am

Thank you!

I did that three times now but unfortunately the problem remains.

What else could I do?

KlausHirsch · March 12, 2018, 3:59am

Just adding a bit more info

KlausHirsch · March 12, 2018, 3:59am

And one more screenshot

cbeams · March 13, 2018, 8:45am

@keo, you’re the arbitrator on this trade. Can you look into what went wrong here and get back to @KlausHirsch, please? Thanks.

keo · March 13, 2018, 6:27pm

KlausHirsch. are your funds in your Bisq wallet correct? I suspect that your db is corrupted. Check what Wallet problems - what to do says. Do not forget to take a backup. Keep me posted how it goes.

Keo

KlausHirsch · March 14, 2018, 7:07am

My database seems to be OK. I checked for wallet problems but couldn’t find anything.
I’ve the feeling something went wrong with the dispute resolution (see screenshot below).

BTC Wallet:
Address entry list:
AddressEntry{offerId=‘null’, context=ARBITRATOR, address=1HF1qpuWmhUGQfnEzXF4E4iwqGpVwLMfbL}
AddressEntry{offerId=‘null’, context=AVAILABLE, address=1MvJQhwSG4zcEojdihY8ed5U6HLDcb4J84}
[several omitted]

AddressEntry{offerId=‘yevb5inj-3745eeee-9390-4849-a20b-f8ebe8e016db-063’, context=MULTI_SIG, address=15k3HJTdkhcG2QeqXkrgZveJdQVDLyCjVn}
AddressEntry{offerId=‘yevb5inj-3745eeee-9390-4849-a20b-f8ebe8e016db-063’, context=TRADE_PAYOUT, address=1JLTtgS5AaAqT3EPedBHnTkMqBiCfnWcu6}

AddressEntry{offerId=‘null’, context=AVAILABLE, address=1cnqzt9musVa85oFD1owLvzkrraZ2V66a}
AddressEntry{offerId=‘null’, context=AVAILABLE, address=15AgnjR51YEdVVxGhyyJYcfXz1JpwgToWF}
[several omitted]

Wallet containing 0.1031352 BTC (spendable: 0.1031352 BTC) in:
0 pending transactions
1 unspent transactions
38 spent transactions
0 dead transactions
Last seen best block: 513456 (2018-03-14T05:56:51Z): 0000000000000000004b81e5ffb9a1d51db1f69f2fc60d8e42b2966f1e772440
Encryption: AES-256-CBC, Scrypt (N: 32768)

-0.0000192 BTC total value (sends 0.088 BTC and receives 0.0879808 BTC)
confidence: Appeared in best chain at height 512537, depth 920. Source: NETWORK
62d6bd70f0c38b721318d6ff5a19b54552d11713a929588850235cde044c922d
updated: 2018-03-08T06:30:39Z
in PUSHDATA(71)[30440220528a9f25c2e47d8c5d814707de36c752460c2691c250156a216dd074146e7775022016883d330e60f3d960bb96f158fa2064e3a45ce6c86f6bf041c3b291bcd6660d01] PUSHDATA(33)[0367ff6abf3356064d443d4a873536ec9c06368c22ae1dc7d729d1eaf8413e772e] 0.088 BTC (8800000)
outpoint:df7269cb785393df5a4d8674caa62fd01d0c9171616ce2da811fca56b7330bb7:1 hash160:be287d35c06fa4c05f5c9f19ef74cae31961c465
out DUP HASH160 PUSHDATA(20)[7c45b9d64147f737f95da95c3253887257bd7acb] EQUALVERIFY CHECKSIG 0.0879808 BTC (8798080) ScriptPubKey: 76a9147c45b9d64147f737f95da95c3253887257bd7acb88ac Address:1CL6KRtrwWZmSzHSRC4RQhFxcbmx3f8cc8 Spent by 3ed344ab4a5d9027366707bd3513ddf3834d8a87c9c680bc256feca7296a03a1
fee 0.0000192 BTC for 191 bytes (10 Satoshi/Byte)
prps UNKNOWN

0.003 BTC total value (sends 0.00 BTC and receives 0.003 BTC)
confidence: Appeared in best chain at height 509027, depth 4430. Source: NETWORK
390e16f808af56619f9a40728b99f96cfe1ce0f8ed6de91baa1d98d34b00ddc9
updated: 2018-02-13T18:17:27Z
in 0 PUSHDATA(71)[304402204a8c932439b5409db6bf7c9440729d459f7105f6212c8827c16bd7c77a201dff02200478df0128bd7222ee6920c4e37cccfcd84476c107af585f3884a474b6010ee301] PUSHDATA(72)[3045022100ca29b85f4b89fb3b9a0396273703686d0716fba86526a0cd36f82c9c871a51ed0220051d2d964331a0d6614c7f086c1437dea3f8027e7bb995908809d8c31b52d07801] PUSHDATA1[522103c573088374ed872253a70565b36c6dc02ed889ca29d5a3e6546c67ccbc52ffd021037803ebcdb6438aaee77b8ba67234828708ed5f2e8e67b297b124d177751278212102e2b9e44d50b043fde40db5ccdb3a568fb15f6442cf73604c04f2c7a8452855a453ae] 0.123224 BTC (12322400)
outpoint:70287f4cc9613404fa617ffc473fbee23bedad92ab883d9121287708add6f117:0 hash160:57c9579542b9e9395cdd97bc7b50898d345e9cd4
out DUP HASH160 PUSHDATA(20)[d13fede7481cab62b6a0bf5dfb105027f5b900ba] EQUALVERIFY CHECKSIG 0.12 BTC (12000000) ScriptPubKey: 76a914d13fede7481cab62b6a0bf5dfb105027f5b900ba88ac Address:1L5Qoyn4FSdKZpkreucmZWUzL9Sdk78WyZ
out DUP HASH160 PUSHDATA(20)[3827c323563e51fd4969e2e23b594392fcb0c3a5] EQUALVERIFY CHECKSIG 0.003 BTC (300000) ScriptPubKey: 76a9143827c323563e51fd4969e2e23b594392fcb0c3a588ac Address:167vUUQtmMa6m1kM7TwPJtd17zDU8zwDcU Spent by 3ed344ab4a5d9027366707bd3513ddf3834d8a87c9c680bc256feca7296a03a1
fee 0.000224 BTC for 374 bytes (59 Satoshi/Byte)
prps UNKNOWN

0.088 BTC total value (sends 0.00 BTC and receives 0.088 BTC)
confidence: Appeared in best chain at height 507165, depth 6292. Source: NETWORK
df7269cb785393df5a4d8674caa62fd01d0c9171616ce2da811fca56b7330bb7
updated: 2018-02-01T22:41:50Z
in 0 PUSHDATA(71)[304402207edda7a5c4b009ec3dbfa4e9b07bd529f8943713331b3074ed1243b4dc1d6ac702203e4da4c7ba9f9422ccccd75d9cfc5e887724f956a3c6fd08302f911ccd41970d01] PUSHDATA(72)[3045022100ce0e2afc57195ca08e8c08be10a6b979ebfd73acb90c716b2f326e88b8eb6f460220492fe6f9f40938b5223b0817dd516f7af7ad00a8862a5f3dea0f9ef7f21ae1b501] PUSHDATA1[522103c573088374ed872253a70565b36c6dc02ed889ca29d5a3e6546c67ccbc52ffd0210286cf2d902ec0c99c941b6438ef564f99ce817420ff5951ffffd7ee1881f30f942103e8cc0b8189e2c0fcec0d594effe1f9fab995e10d429ba1e04a67cc2a3643123e53ae] 0.0985681 BTC (9856810)
outpoint:075087bf22cb5a273ecc8195063cf880faefc1810313bbf86caa932b004e1d76:0 hash160:3684e7a8fb68cff372d552ef33deafd5fb248dda
out DUP HASH160 PUSHDATA(20)[c9139c57e09720217f3ab740808e3cc045ac46a3] EQUALVERIFY CHECKSIG 0.01 BTC (1000000) ScriptPubKey: 76a914c9139c57e09720217f3ab740808e3cc045ac46a388ac Address:1KLCK8nvt3YE8ZeX595LVgZGVTwqy9JEDW
out DUP HASH160 PUSHDATA(20)[be287d35c06fa4c05f5c9f19ef74cae31961c465] EQUALVERIFY CHECKSIG 0.088 BTC (8800000) ScriptPubKey: 76a914be287d35c06fa4c05f5c9f19ef74cae31961c46588ac Address:1JLTtgS5AaAqT3EPedBHnTkMqBiCfnWcu6 Spent by 62d6bd70f0c38b721318d6ff5a19b54552d11713a929588850235cde044c922d
fee 0.0005681 BTC for 374 bytes (151 Satoshi/Byte)
prps UNKNOWN

-0.088 BTC total value (sends 0.088 BTC and receives 0.00 BTC)
confidence: Appeared in best chain at height 506489, depth 6968. Source: NETWORK
075087bf22cb5a273ecc8195063cf880faefc1810313bbf86caa932b004e1d76
updated: 2018-01-28T11:44:39Z
in PUSHDATA(72)[3045022100f9eb6b20d1db88c5c4eb1f2784833ef73704ae370ca90b403979d2eb0c98497a02203c6b1554c73b1a27f7ccfc7afbccdf94ab4c738f431f738bc00510ef25730a2b01] PUSHDATA(33)[0200b0211cf8df7a79388b21283bc859c9dc34c63c6881a84e642efe6ebb152435]
outpoint:d6159a3f407e6f6fa406512d250ce58a8e33ff31ee0b013ab55637a69738c3b2:1
in PUSHDATA(72)[30450221008b114f1be621e3ac72c74798860bace21a9633192f45bd72e8b9c8138059d4bc02205208c985d5b6025c121961e2cf156adb9ed3badc1ab54a9cf65358007875e7ed01] PUSHDATA(33)[022c5bd0d2f03e687a0619e56a1315ab77790f9b5f634a0f6bdafa664ec15dc355] 0.088 BTC (8800000)
outpoint:43d3bcac248d16bdac06131f7b41b43190db1d94a106b5ecd02ec6fd2fb04f0a:1 hash160:06c4d3f5b8b1d08dbb2ea1a175c442760e38b2aa
out HASH160 PUSHDATA(20)[3684e7a8fb68cff372d552ef33deafd5fb248dda] EQUAL 0.0985681 BTC (9856810) ScriptPubKey: a9143684e7a8fb68cff372d552ef33deafd5fb248dda87 Address:36fHdJGLzeaxrZ9PjoirqMaPCedRjXS7yD Spent by df7269cb785393df5a4d8674caa62fd01d0c9171616ce2da811fca56b7330bb7
out RETURN PUSHDATA(32)[917fbd2b634dda5ad81ba60ec1c223bde06e1bb27fc8fd68b827231d5d4b508f] 0.00 BTC (0) ScriptPubKey: 6a20917fbd2b634dda5ad81ba60ec1c223bde06e1bb27fc8fd68b827231d5d4b508f Address:[exception: Cannot cast this script to a pay-to-address type]
prps UNKNOWN

-0.00033 BTC total value (sends 0.50091 BTC and receives 0.50058 BTC)
confidence: Appeared in best chain at height 506445, depth 7012. Source: NETWORK
43d3bcac248d16bdac06131f7b41b43190db1d94a106b5ecd02ec6fd2fb04f0a
updated: 2018-01-28T02:39:30Z
in PUSHDATA(72)[3045022100b40035ce97fd7240eedeb1e579191ca061002d1cc1137a83ec64903eedad9de20220095d5987d3af7b5fae0c7b27468d5ccdb5113cfa1d453da952e14ed3330721ea01] PUSHDATA(33)[02a3bb8206af1973b2aae5c48ca84a9a3e7d94a0614a52fb095b259427036a0974] 0.50091 BTC (50091000)
outpoint:e600b7361511feae007d190c020b4463387e2115f044f566e5c8d5e837ec871c:2 hash160:e57717fdf9e04d31987cf1692ebef75aa8c7598b
out DUP HASH160 PUSHDATA(20)[4fceee700a31f782ba4f9ebd2b127cd400041bb1] EQUALVERIFY CHECKSIG 0.0002 BTC (20000) ScriptPubKey: 76a9144fceee700a31f782ba4f9ebd2b127cd400041bb188ac Address:18GzH11T5h2fpvUoBJDub7MgNJVw3FfqQ8
out DUP HASH160 PUSHDATA(20)[06c4d3f5b8b1d08dbb2ea1a175c442760e38b2aa] EQUALVERIFY CHECKSIG 0.088 BTC (8800000) ScriptPubKey: 76a91406c4d3f5b8b1d08dbb2ea1a175c442760e38b2aa88ac Address:1cnqzt9musVa85oFD1owLvzkrraZ2V66a Spent by 075087bf22cb5a273ecc8195063cf880faefc1810313bbf86caa932b004e1d76
out DUP HASH160 PUSHDATA(20)[e57717fdf9e04d31987cf1692ebef75aa8c7598b] EQUALVERIFY CHECKSIG 0.41258 BTC (41258000) ScriptPubKey: 76a914e57717fdf9e04d31987cf1692ebef75aa8c7598b88ac Address:1MvJQhwSG4zcEojdihY8ed5U6HLDcb4J84 Spent by ca46ba66d33d945e46ddb65fef3cf2eac8ca195b7ffd6ca9b65643dfb2690dbd
fee 0.00013 BTC for 260 bytes (50 Satoshi/Byte)
prps UNKNOWN

keo · March 14, 2018, 5:12pm

I reopened and closed the ticket. Did it help?
I don’t understand what you mean by “I checked for wallet problems but couldn’t find anything.”?
Is the balance of the wallet correct assuming that the 0.088 btc in the “Locked in trades” is in fact 0 btc?
As far as I can see from my peer the payout worked as it should.

KlausHirsch · March 18, 2018, 10:55pm

Thanks for looking into that.

Reopening and closing the ticket stopped my Bisq client from starting since it detected duplicate transactions.

I uninstalled Bisq, reinstalled it and copied my wallet backup to the new Bisq installation.

Is the balance of the wallet correct assuming that the 0.088 btc
in the “Locked in trades” is in fact 0 btc?

Yes, it is.

Now I am where I was two weeks ago. Bisq starts but says that that 0.088 BTC are locked in trades and trade ID “yevb5inj-3745eeee-9390-4849-a20b-f8ebe8e016db-063” is shown in open trades but I can’t get rid if it.

keo · March 19, 2018, 10:10am

If you want you can send your btc from the Bisq wallet to an external wallet and do a clean install after deleting your Bisq directories. You will then lose your history etc. If you want to do a more gentle cleanup you must get help from e. g. alexej966 or Manfred. Something is corrupted.

Keo

keo · March 19, 2018, 10:11am

btw, if you want to do a full reinstall close all open offers etc.

KlausHirsch · March 19, 2018, 8:06pm

OK, thank you.
I’ll consider sending BTC from my Bisq wallet to an external wallet and do a clean install after deleting all my Bisq directories. Only reason that I haven’t done it yet is that I’m not fond of losing my history.

alexej996 · March 20, 2018, 8:46pm

It is a good practice to never really delete your wallets, but move them somewhere safe instead, just in case. Bisq’s data directory has a wallet file, so you probably shouldn’t delete it either, just move it somewhere else.