[bisq-network/proposals] "One Cancels Other (OCO)" option to reduce reserved BTC requirements (Issue #370)
Conza
notifications at github.com
Sun Mar 20 09:04:57 CET 2022
> I think an easier model would be to allow multiple payment methods to one offer. But also that would come with quite some dev effort.
What can be done in Bisq 1 that would allow that, get it over the line? If I and a few others threw some more money at it?
I am not necessarily directly interested in OCO; but whatever can get the job done as end result:
- Buyers/sellers can put in offers in their local markets; in whatever methods they like, and also in other markets. At the same time.
I would have thought when one is taken; in that reserve/batch/group the others disappear, and the buyer/seller can they easily re-create if they wish. Or if they already have made other single offers (with other multiple payment methods etc.), they would remain until one from that batch/group/ is taken.
What would a possible bare minimum be possible?
--
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/370#issuecomment-1073193316
You are receiving this because you are subscribed to this thread.
Message ID: <bisq-network/proposals/issues/370/1073193316 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20220320/ba6f9eb9/attachment.htm>
More information about the bisq-github
mailing list