You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 13, 2022. It is now read-only.
Sending the !fill messages in serial might have a big benefit for Takers. Instead of selecting all orders at the start and keeping with them they could select new orders each time a Maker responds.
Taker selects new orders: selectOrders(include=[O1, O2], ignore=[M3])
Taker's new orders are O1, O2, O6, O7 from Makers M1, M2, M6, M7
Repeat until all orders are filled
...
Possibly a similar process for !tx and !sig responses (too late because of PoDLE blacklisting by Makers?)
This would be a large help with the problem of Takers running out of commitments. They would not need a new commitment due to any number of Makers not responding. And they would nearly always get the number of Makers they wanted and minimum_makers would only be needed if there were not enough matching orders from responding Makers in the orderbook.
Implementing this would require the change in #723. If the suggestions there are used (e.g. commitment can be used 10 times) then Taker would be able to dynamically select orders up to 10 times using a single commitment (probably more since Makers that don't respond will also probably not broadcast the commitment).
Sending orders in serial would also prevent the Sybil style attack described in #693 (comment)
The text was updated successfully, but these errors were encountered:
Sending the !fill messages in serial might have a big benefit for Takers. Instead of selecting all orders at the start and keeping with them they could select new orders each time a Maker responds.
...
This would be a large help with the problem of Takers running out of commitments. They would not need a new commitment due to any number of Makers not responding. And they would nearly always get the number of Makers they wanted and minimum_makers would only be needed if there were not enough matching orders from responding Makers in the orderbook.
Implementing this would require the change in #723. If the suggestions there are used (e.g.
commitment
can be used10 times
) then Taker would be able to dynamically select orders up to 10 times using a single commitment (probably more since Makers that don't respond will also probably not broadcast the commitment).Sending orders in serial would also prevent the Sybil style attack described in #693 (comment)
The text was updated successfully, but these errors were encountered: