[bisq-network/proposals] Investigate alternative implementation for bisq (as basis for V2 / off-chain trading) (#125)

ExPrgrmmr notifications at github.com
Wed Nov 13 05:34:55 UTC 2019


> Further the initial view that Bisq v2 requires a hard fork must not be taken as “fact” but as first "educated guess". It might be that we find ways to integrate it in Bisq v1 and/or deploy it without hard fork as we found a way to deploy the new trade protocol (1.2) without a hard fork.

That legacy v2 needs a hard fork is facts until you deliver proof for the opposite. Approval of legacy v2 includes guesses about v1 in the proposal. Instead an integration proposal and/or separation proposal should be made and voted on.

Deploying the new trade protocol (v1.2) can't be compared because it is not an integration rather changed functionality.

Furthermore, now with the v2 proposals we have proposals on proposals (on proposals) which is not good for getting anything done, creating this kind of feuds.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/125#issuecomment-553247084
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191112/017d984c/attachment.html>


More information about the bisq-github mailing list