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

[w0000000t]

As I said on matrix (but let's make this official on GH) I like this approach very much, as it doesn't need to overhaul the current UI for offer making, but rather recycles most of it, just adding the grouping field.
The "grouping" concept is the name I came up with, as I know there is a service named Gixen that is used to "snipe" on ebay auctions, and you can set snipes for multiple items on ebay, grouping them (groups are numbered, 0, 1, 2...) so that as soon as one auction snipe wins an item in a group, all other snipes in the same group are removed.

I am a DIY programmer even if I don't use Java, so I can see how this would be way easier on the backend, as there would just be the need, on offer being taken, to recurse over the open offers, to disable/delete the ones with the same group of the one that's just been taken. On the UI front, it's even easier as there's a text field to be saved in the offer properties, and nothing more.

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

Message ID: <bisq-network/proposals/issues/370/1066951549 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20220314/1608835c/attachment-0001.htm>