[bisq-network/proposals] Proposal to increase liquidity on Bisq by allowing each offer to have multiple payment methods and currencies associated with it. (#288)

apemithrandir notifications at github.com
Fri Mar 11 05:56:35 CET 2022


My interpretation of the core issue is that we desire to empower users to be able to leverage their reserve more by being able to post conditional offers to the order book and reduce their reserve requirements as a result.

At present if you post many offers you must reserve btc for each offer. The proposal here would allow users to create a special new order type linking a single reserve to multiple conditional offers at the time of offer creation.

My concerns over the present proposal would be the added complexity and potential reduced usability of the Create Offer page. Also the length of time and work required to implement the UI changes to the Create Offer page.

There will be trade-offs with any approach, but I would like to propose a slightly different approach.
- When creating an offer you can assign a group/tag to that offer
- You could reuse that group/tag when creating new offers
- You add more btc to the reserve only if the reserve of your new offer exceeds the maximum reserve of all existing offers under that group/tag
- Every offer under that group/tag is conditional on each other being live
- If you trade one the rest will cancel and excess reserve will be returned immediately
- Some allowances should be made to reduce the fee burden of these cancelled orders (though I'm unsure how to achieve this)

This approach will preserve the maximum flexibility of setting all these features per offer:
![image](https://user-images.githubusercontent.com/99969638/157804177-66800e74-26f8-4d45-9c7f-c4440b3b5ca5.png)
while reducing the need to over engineer and crowd the create offer page.

Downsides would be that power users would lack the ability to easily create bulk orders in the UI. Though I would contend that a true power user should be able to do this via the API.

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

Message ID: <bisq-network/proposals/issues/288/1064772509 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20220310/47b4078e/attachment.htm>


More information about the bisq-github mailing list