<p>and I personally feel we should revert the feature for now and re-evaluate it (with heavy testing) before merging it back into master. The most important thing is to keep Bisq stable and we must be risk averse when it comes to these types of changes.</p>
<p>That was my first intention, but the problem with reverting this feature is that unfortunately too much code touching this parts of the codebase occurred, so I can't just revert it by the GitHub feature. So it would also need lots of manual code changes which are also error-prone as well. I agree that keeping Bisq stable is key, so I think for the future we should also discuss having more devs than just two involved in release testing. In our last three releases we always had issues based on very specific OS setups. That can only be detected if lots of people are at least starting and smoke testing new releases. In short for the v1.2.9 update I think we need to go with the best local bitcoin node detection solution we can come up with.</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/pull/4058#issuecomment-598811564">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNXVYIYPIGHH3MD75WTRHJORLANCNFSM4LHEHKSA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNTISVB5T6KT3AJ7KSLRHJORLA5CNFSM4LHEHKSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOYSHLA.gif" height="1" width="1" alt="" /></p>
"name": "View Pull Request"
"description": "View this Pull Request on GitHub",