<p></p>
<p>The <code>Invalid input length 63</code> happens when you're missing a digit on the txid.  I'll add validation checks to handle this better in the related work for <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="581160352" data-permission-text="Title is private" data-url="https://github.com/bisq-network/bisq/issues/4061" data-hovercard-type="issue" data-hovercard-url="/bisq-network/bisq/issues/4061/hovercard" href="https://github.com/bisq-network/bisq/issues/4061">#4061</a>.</p>
<hr>
<p>The more important issue, however, is that a transaction was published but <em>rejected silently with no error</em> and no information in the log.  This I think is a potential can of worms.  It could be the cause of those many user reports that trades are created but the transaction never confirms and never shows up in the mempool.</p>
<p>I think a good start to tracking this down would be to log the hex of all transactions generated by Bisq at the point where they are broadcasted by BitcoinJ.  Then when a user experiences the problem at least we'll be able to check the transaction hex and see by comparing it to the blockchain why it was not accepted into the mempool.  At the moment only textual "description" of the transaction is logged which is not sufficient for problem solving.  I'll work up a PR for this.</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/4878#issuecomment-738013955">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNUNN5FQ4UVMN6CZRADSS6LGPANCNFSM4ULDGEXA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNRJRMFLEAKAKZ5YY3DSS6LGPA5CNFSM4ULDGEXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFP6TGAY.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/4878#issuecomment-738013955",
"url": "https://github.com/bisq-network/bisq/issues/4878#issuecomment-738013955",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>