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
This simply needs to be specified exactly in the specification.
We need to make sure that we have sequential processes: pricecaculations, and deposits and withdrawals. they can not happen in parallel
The text was updated successfully, but these errors were encountered:
bh2smith
changed the title
We need to ensure that there are timeslots for withdrawals
Must ensure there time-slots available for withdrawal
Jan 17, 2019
To elaborate a bit more, there are two (somewhat) contradictory paragraphs
The first stating that account states can't change during price finding.
Participants can provide state transitions that apply pending deposits and withdrawals only while the order collection process is ongoing (the current batch is not yet frozen). Since price finding and order matching is a computationally expensive task, the account state must not change while the optimization problem is ongoing, as this could potentially invalidate correct solutions (e.g. a withdraw could lead to insufficient balance for a matched trade). As soon as the matching of a closed batch is applied, pending withdrawls and deposits can again be applied to the state.
and later on,
After a certain time-frame or once the maximum number of orders per batch are collected, a batch is "frozen" and the orders participating in it are final. A new batch could immediately start collecting new orders while the previous one is being processed.
This simply needs to be specified exactly in the specification.
We need to make sure that we have sequential processes: pricecaculations, and deposits and withdrawals. they can not happen in parallel
The text was updated successfully, but these errors were encountered: