<p></p>
<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/cbeams/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/cbeams">@cbeams</a> discussions with the chimp at the time indicated that updating bitcoinj was so arduous and time-consuming (at least for the purpose of supporting segwit) that it didn't make sense to make it a priority given all the other high priorities of the project.</p>
<p>The Bisq v2 proposal from that time was also a consideration (i.e., seemed better to spend resources to develop and build that instead of maintaining bitcoinj in Bisq v1).</p>
<p>I think 1 or 2 folks had come by expressing interest in the role (not sure how serious) and weren't met with a whole lot of interest.</p>
<p>Taking all of this into account, it didn't make sense to keep the role marked as <code>help-wanted</code>.</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/roles/issues/8#issuecomment-612902726">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNX2ONXM6GZQUCGG7GDRMMI4VANCNFSM4DZPNBRQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNV5ORAYA4TK4OC5MUDRMMI4VA5CNFSM4DZPNBR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOESECORQ.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/roles/issues/8#issuecomment-612902726",
"url": "https://github.com/bisq-network/roles/issues/8#issuecomment-612902726",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>