[bisq-network/proposals] "One Cancels Other (OCO)" option to reduce reserved BTC requirements (Issue #370)

[w0000000t]

> Your suggestion would come with considerable dev effort IMO.

Could you explain even in a very short manner how you envision this "grouping" liquidity increase as a significant development effort?
My knowledge is currently limited to the LAMP stack, so it's possible this skews my perception of the complexity of implementing this mechanism on top of the current Bisq with Java

-- 
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/370#issuecomment-1069203449
You are receiving this because you are subscribed to this thread.

Message ID: <bisq-network/proposals/issues/370/1069203449 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20220316/105cf084/attachment.htm>