Solver routing
How solvers bid against commitments and split execution across shielded hops.
Registered solvers receive intents encrypted under a threshold key held by the settlement committee. A solver decrypts only the routing-relevant fields inside a TEE-free MPC round, computes a candidate route, and submits a sealed bid consisting of a committed output amount and a proof that the route is executable against current pool state.
| Step | Provable / public | Hidden |
|---|---|---|
| Intent broadcast | cm, encrypted payload size (padded) | Pair, size, direction |
| Sealed bid | Bid commitment, solver id | Route, quoted output |
| Winner selection | Winning bid commitment | Losing bids |
| Hop split | Aggregate transition | Per-hop amounts, ordering |
Routes are split across up to three intermediate shielded nodes (nf:*), each of which is a note transfer rather than a public swap, so no individual hop exposes the full path.