<p>I believe <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=8533296" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/bodymindarts">@bodymindarts</a> is doing a great job rewriting the <code>Bisq</code> protocol in Rust. Don't get me wrong, <code>Bisq</code> is awesome and the current Java implementation was great to launch the project and to onboard new users.</p>
<p>But there are issues. It has highly coupled components, making it difficult to extend, refactor or test. I'm following threads here on API implementation for more than a year already and I see how difficult is to make it work with current architecture. There were already several PRs that were rejected due to the number of changes needed to be done. I can imagine this might demotivate developers to continue the work and makes it difficult to attract new ones. Also, the current implementation is unsuitable for constrained hardware, such as Raspberry Pi, as it consumes a lot of resources. Some dependencies are outdated and unmaintained, the aforementioned BitcoinJ is just the most critical example. Not to say we have to stick with JDK10 which is not even LTS and might have security issues.</p>
<p>Besides the technical part, things like "Everyone should upgrade to version X before date Y because trading protocol will stop working" don't sound like decentralized governance to me. The modular, independent implementation (or better several implementations) will allow people to use only those features that they really need. For example, to me altcoins trading and GUI make little sense, and I know that I'm not alone. :) Also, not locking the project to the sole ecosystem and porting it to different architectures would help the protocol maturity IMHO.</p>
<p>We should encourage more independent implementations!</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/proposals/issues/125?email_source=notifications&email_token=AJFFTNRFCPIPIWL5X7KGYYTQNM5SBA5CNFSM4I5MQO72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAQNM7I#issuecomment-539022973">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNWWXPEQEQHFTHDRULLQNM5SBANCNFSM4I5MQO7Q">mute the thread</a>.<img src="https://github.com/notifications/beacon/AJFFTNTDIIFNR2ZCZ4KU4M3QNM5SBA5CNFSM4I5MQO72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAQNM7I.gif" height="1" width="1" alt="" /></p>
"name": "View Issue"
"description": "View this Issue on GitHub",