Epochs
PublicClearing runs in epochs rather than continuously, because a continuous match is a stream of observable events and a batch is one.
No epochs yet
Connect a Safe and the epochs its orders joined will appear here.
Floors
Read from the deployed engine, not repeated here.
Participants before the epoch may publish anything at all
Contributors before an unmatched remainder may reach Uniswap
Contributors before an aggregate may reach the pooled Aave position
The residual and supply floors are counted separately. Sharing one would let a two-contributor swap authorise a one-contributor supply.
What an epoch does
- 1
Open
The epoch accepts candidates. Orders join by being authorised.
- 2
Sealed
The candidate set is fixed and sorted. No order can be added or moved.
- 3
Price fixed
A TWAP snapshot is captured from the pool, with its block and cardinality recorded.
- 4
Computing
Locking, gating, crossing and residual accumulation, all inside Nox.
- 5
Residual ready
The floors are met and the published handles are committed.
- 6
Settling
The aggregate reaches a reviewed adapter, then allocations reconcile.
- 7
Settled
Every candidate holds an encrypted outcome only its Safe can read.
Why the price is time-weighted rather than spot
Internal crossing moves value between treasuries at a price nobody outside can see. A wrong price is still confidential, it just moves the wrong amount from a Safe that cannot tell to a Safe that cannot tell either. So the reference is a 30 minute mean with a 1000 tick deviation bound, checked for staleness at settlement rather than at capture.