Inconsistent spend tx

[pmknutsen]

Attempted to create a new trade. Wallet had insufficient funds. Move over funds from other wallet and continued with the trade setup before incoming tx confirmed. Then got this error:

Inconsistent spent tx: 36e84021e40eb9b6ccd95c4f684384cd28b9b6b606426d3a27c909c10e012c80

Here is what I think is the relevant part from logs:

tradingFeeTx:
  154b019f2c909b022d8e1c2eb3306696bcc9b856cc489a4d671c8a7fd5f1f573
     in   PUSHDATA(72)[3045022100c57ce09351b37c07de83bfbdada54b203cd3d4b9152b19a1a2f828d62566235902203a1e42ed19927f0e17f321069814cfd84f80022889452bdee674ec65bea38cda01] PUSHDATA(33)[02372d23a9db6d50aa7f54af8c2831e6c42e092f6f1d667993793e29e7bcd3c8a9] 0.0817296 BTC (8172960)
          outpoint:fc9867de37c837dfd7f3ff71e84791f0d0b40f2a92bbf6ecf4f59d6f32b451d6:2 hash160:8c290384ad1fb8f1743bdae3a114b691106e2e75
     out  DUP HASH160 PUSHDATA(20)[f6876dfc59041e46bdaece49428676dd9e5b3226] EQUALVERIFY CHECKSIG 0.001 BTC (100000) ScriptPubKey: 76a914f6876dfc59041e46bdaece49428676dd9e5b322688ac Address:1PUXU1MQ82JC3Hx1NN5tZs3BaTAJVg72MC 
     out  DUP HASH160 PUSHDATA(20)[c4b836808ab3caf238bd9182ce7ba99c87694555] EQUALVERIFY CHECKSIG 0.01 BTC (1000000) ScriptPubKey: 76a914c4b836808ab3caf238bd9182ce7ba99c8769455588ac Address:1JwA7wFZtDftTuFZNFa5iZxsDsBys1zUSv 
     out  DUP HASH160 PUSHDATA(20)[7ffe888706770d9cbcfd4a47a3de536a2afb7cbd] EQUALVERIFY CHECKSIG 0.0705944 BTC (7059440) ScriptPubKey: 76a9147ffe888706770d9cbcfd4a47a3de536a2afb7cbd88ac Address:1CfmjeXCaRQnbERYQHzDsZMbDLaaicqNX2 
     fee  0.0001352 BTC for 260 bytes (52 Satoshi/Byte)
     prps USER_PAYMENT
 
Apr-20 16:45:32.111 [JavaFX Application Thread] INFO  o.b.w.Wallet: commitTx of 154b019f2c909b022d8e1c2eb3306696bcc9b856cc489a4d671c8a7fd5f1f573 
Apr-20 16:45:32.111 [JavaFX Application Thread] INFO  o.b.w.Wallet:   marked fc9867de37c837dfd7f3ff71e84791f0d0b40f2a92bbf6ecf4f59d6f32b451d6:2 as spent by 154b019f2c909b022d8e1c2eb3306696bcc9b856cc489a4d671c8a7fd5f1f573 
Apr-20 16:45:32.111 [JavaFX Application Thread] INFO  o.b.w.Wallet: ->pending: 154b019f2c909b022d8e1c2eb3306696bcc9b856cc489a4d671c8a7fd5f1f573 
Apr-20 16:45:32.111 [JavaFX Application Thread] INFO  o.b.w.Wallet: Estimated balance is now: 0.1280944 BTC 
Apr-20 16:45:32.111 [JavaFX Application Thread] WARN  b.c.b.w.TradeWalletService: Balance = 7059440; CoinSelector = bisq.core.btc.wallet.BtcCoinSelector@3fe4594f 
Apr-20 16:45:32.112 [JavaFX Application Thread] WARN  b.c.b.w.TradeWalletService: createBtcTradingFeeTx failed: tradingFeeTx=  154b019f2c909b022d8e1c2eb3306696bcc9b856cc489a4d671c8a7fd5f1f573
  updated: 2019-04-20T14:45:32Z
     in   PUSHDATA(72)[3045022100c57ce09351b37c07de83bfbdada54b203cd3d4b9152b19a1a2f828d62566235902203a1e42ed19927f0e17f321069814cfd84f80022889452bdee674ec65bea38cda01] PUSHDATA(33)[02372d23a9db6d50aa7f54af8c2831e6c42e092f6f1d667993793e29e7bcd3c8a9] 0.0817296 BTC (8172960)
          outpoint:fc9867de37c837dfd7f3ff71e84791f0d0b40f2a92bbf6ecf4f59d6f32b451d6:2 hash160:8c290384ad1fb8f1743bdae3a114b691106e2e75
     out  DUP HASH160 PUSHDATA(20)[f6876dfc59041e46bdaece49428676dd9e5b3226] EQUALVERIFY CHECKSIG 0.001 BTC (100000) ScriptPubKey: 76a914f6876dfc59041e46bdaece49428676dd9e5b322688ac Address:1PUXU1MQ82JC3Hx1NN5tZs3BaTAJVg72MC 
     out  DUP HASH160 PUSHDATA(20)[c4b836808ab3caf238bd9182ce7ba99c87694555] EQUALVERIFY CHECKSIG 0.01 BTC (1000000) ScriptPubKey: 76a914c4b836808ab3caf238bd9182ce7ba99c8769455588ac Address:1JwA7wFZtDftTuFZNFa5iZxsDsBys1zUSv 
     out  DUP HASH160 PUSHDATA(20)[7ffe888706770d9cbcfd4a47a3de536a2afb7cbd] EQUALVERIFY CHECKSIG 0.0705944 BTC (7059440) ScriptPubKey: 76a9147ffe888706770d9cbcfd4a47a3de536a2afb7cbd88ac Address:1CfmjeXCaRQnbERYQHzDsZMbDLaaicqNX2 
     fee  0.0001352 BTC for 260 bytes (52 Satoshi/Byte)
     prps USER_PAYMENT
, txOutputs=[TxOut of 0.001 BTC to 1PUXU1MQ82JC3Hx1NN5tZs3BaTAJVg72MC script:DUP HASH160 PUSHDATA(20)[f6876dfc59041e46bdaece49428676dd9e5b3226] EQUALVERIFY CHECKSIG, TxOut of 0.01 BTC to 1JwA7wFZtDftTuFZNFa5iZxsDsBys1zUSv script:DUP HASH160 PUSHDATA(20)[c4b836808ab3caf238bd9182ce7ba99c87694555] EQUALVERIFY CHECKSIG, TxOut of 0.0705944 BTC to 1CfmjeXCaRQnbERYQHzDsZMbDLaaicqNX2 script:DUP HASH160 PUSHDATA(20)[7ffe888706770d9cbcfd4a47a3de536a2afb7cbd] EQUALVERIFY CHECKSIG] 
Apr-20 16:45:32.112 [JavaFX Application Thread] ERROR b.c.t.Task: An error occurred at task: CreateMakerFeeTx
Exception message: Inconsistent spent tx: 36e84021e40eb9b6ccd95c4f684384cd28b9b6b606426d3a27c909c10e012c80 
Apr-20 16:45:32.112 [JavaFX Application Thread] ERROR b.c.t.TaskRunner: Task failed: CreateMakerFeeTx / errorMessage: An error occurred at task: CreateMakerFeeTx
Exception message: Inconsistent spent tx: 36e84021e40eb9b6ccd95c4f684384cd28b9b6b606426d3a27c909c10e012c80 
Apr-20 16:45:32.112 [JavaFX Application Thread] ERROR b.c.o.p.PlaceOfferProtocol: An error occurred at task: CreateMakerFeeTx
Exception message: Inconsistent spent tx: 36e84021e40eb9b6ccd95c4f684384cd28b9b6b606426d3a27c909c10e012c80 
Apr-20 16:45:32.112 [JavaFX Application Thread] ERROR b.d.m.o.c.CreateOfferDataModel: An error occurred at task: CreateMakerFeeTx
Exception message: Inconsistent spent tx: 36e84021e40eb9b6ccd95c4f684384cd28b9b6b606426d3a27c909c10e012c80 ```

[pmknutsen]

Update: Hit to "Cancel" offer. Then got Warning: "You have already funded that offer". Continued to have funds returned to wallet but balances now longer match with what it what before starting the offer.

[sqrrm]

Looks like an exception from bitcoinj. Do you have any more background information on the wallet, what kinds of transaction in and out and internally, have you used BSQ with the same app?

I'm not great with bitcoinj but I'll take another look, @oscarguindzberg might know more.

[oscarguindzberg]

Some technical details:
36e84021e40eb9b6ccd95c4f684384cd28b9b6b606426d3a27c909c10e012c80 is a tx mined in January 2018.
Neither 154b019f2c909b022d8e1c2eb3306696bcc9b856cc489a4d671c8a7fd5f1f573
nor fc9867de37c837dfd7f3ff71e84791f0d0b40f2a92bbf6ecf4f59d6f32b451d6 were broadcasted to the btc network.

Advise to user:
Your bisq btc (bitcoinj) wallet is inconsistent.
Please, do a backup of your data dir and then do a restore from seed.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.