<p></p>
<p>The wallet being read is in fact corrupt.<br>
Maybe not corrupt in the sense of i/o error while writing it. Corrupt in the sense it is not consistent.<br>
There is a tx output that is marked as spent by some txId and the tx for that txId is not present in the wallet.<br>
maybe useful:</p>
<ul>
<li><a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="324819483" data-permission-text="Title is private" data-url="https://github.com/bitcoinj/bitcoinj/issues/1582" data-hovercard-type="issue" data-hovercard-url="/bitcoinj/bitcoinj/issues/1582/hovercard" href="https://github.com/bitcoinj/bitcoinj/issues/1582">bitcoinj/bitcoinj#1582</a></li>
<li><a href="https://groups.google.com/g/bitcoinj/c/CW7mTHhe_nQ/m/2bpsZP9XCQAJ" rel="nofollow">https://groups.google.com/g/bitcoinj/c/CW7mTHhe_nQ/m/2bpsZP9XCQAJ</a></li>
</ul>
<p>Both links mention 2 wallets. That makes me think of BSQ and BTC wallets in bisq. Maybe the same tx instance is being saved by both wallets. Maybe related <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="393901682" data-permission-text="Title is private" data-url="https://github.com/bisq-network/bitcoinj/issues/18" data-hovercard-type="pull_request" data-hovercard-url="/bisq-network/bitcoinj/pull/18/hovercard" href="https://github.com/bisq-network/bitcoinj/pull/18">bisq-network/bitcoinj#18</a> and <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="396274059" data-permission-text="Title is private" data-url="https://github.com/bisq-network/bitcoinj/issues/21" data-hovercard-type="pull_request" data-hovercard-url="/bisq-network/bitcoinj/pull/21/hovercard" href="https://github.com/bisq-network/bitcoinj/pull/21">bisq-network/bitcoinj#21</a></p>
<p>I found a bug in bisq a month ago. Transaction inputs and outputs have a concept of parent transaction. Parent transaction is the tx containing the input or output. The bisq code used it as if the parent tx was the tx the input was spending from. It would be good to investigate whether this bug is present somewhere else in bisq.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/bisq/issues/4995#issuecomment-750427455">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNSWCVGVNSH3SJYMWMLSWI3R7ANCNFSM4VG5LJ3Q">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNXHJJKWTUOO6GWYX53SWI3R7A5CNFSM4VG5LJ32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFS5J2PY.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/issues/4995#issuecomment-750427455",
"url": "https://github.com/bisq-network/bisq/issues/4995#issuecomment-750427455",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>