Execution
Horizon
What is below the horizon cannot be seen. The name carries its own caveat, and that is the point of choosing it: the horizon is not where geometry puts it. Refraction lifts things over it.
What it does
- ✓An order is submitted as a commitment first and revealed second, so its contents are not in the mempool while it is queued.
- ✓Commitments are halted by Stow. Neither exit is, which is the point of having an emergency stop.
- ✓The commitment is a single hash; the contract stores when it arrived and nothing else.
What it does not
- ×It does not hide that you committed, or when, or from which address.
- ×It does not make you one of many. What protects an order is how many others it could have been, and on a quiet block that number can be one.
- ×It does not survive a sequencer that reorders on content it can see after the reveal.
- ×There is no solver network behind it. See the state table.
There is a version of this page that says “MEV-aware execution with zero-knowledge privacy and gas abstraction” and stops. It is not that the words are wrong; it is that none of them is a quantity, and the quantity — how many orders yours could have been — is the only thing that decides whether any of it worked.