Run the plain public path and mark the moment pending becomes shared state.
MEV & Ordering Free Lab
Submit a user swap, inspect public or private visibility, build a block order, and compare output protection with searcher and proposer balances. Every asset is virtual.
Who gets to choose the order?
Put one swap into a deterministic pool, then watch visibility, ordering, slippage protection, and extraction change the result.
- 01Mempoolintent is visible→
- 02Block orderwho goes first→
- 03Statereplayed by nodes
A mempool record is not a fill. The block order is not a payout. Only execution moves balances and pool reserves.
Searcher profit, proposer tip, pool fees, and user output live on the same ledger.
Submit one user swap first. The key question is not whether the transaction is valid, but who can see and order it before it becomes shared state.
- 01
Public pool created: 120,000 credits + 1,000 TOKEN, any public transaction can change the next quote.
Use the slider to return to an earlier step. Continuing from there replaces the later history with a new sequence.
Try these four ordering experiments.
Run a sandwich with a loose guard, then tighten minimum output until the victim reverts.
Run the back-run and keep pool reserves, searcher P/L, and proposer tip on one ledger.
Repeat the same swap through private flow and name the trust boundary that remains.