Clear the batch, prove it, keep the fee
A solver computes each batch’s clearing and proves it. Anyone with stake behind them can run one, and the first valid clearing posted for a batch is the one that stands.
What a solver does each batch
Read
A batch seals 10 slots after its first order. The node reads its orders and the liquidity it clears against.
Solve
It searches for the price vector that satisfies the four clearing conditions, inside each token’s band.
Clear
It sends
clear_batchwith the prices. The program locks bond equal to the value the batch moves, and orders settle from that moment.Prove
It proves the clearing in the zkVM and sends
prove_batchinside the proof window, 300 slots. The bond unlocks and the clearing fee is paid.
What it needs
Stake
Free bond at least as large as the batches it clears. It comes from the operator and from stakers who choose the solver. The bond is SOL and liquid staking tokens, valued in SOL at the stake pool’s own rate.
The node
The solver node is the operator’s tool: it follows sealed batches, solves, posts and proves. It shares its clearing library with the guest, so it posts only results the guest will prove.
A prover
SP1 Groth16 proofs of the guest, from the operator’s own hardware or from a prover network, landing inside the proof window for every batch cleared.
What it earns
A fraction of each filled order’s output. The solver that cleared the batch receives it when the proof verifies, keeps its commission, and the rest goes to its stakers.
The operator sets the commission when the solver registers. A lower commission pays stakers more of each batch, and more stake behind a solver is more free bond, which is more and larger batches it can clear at once.
A solver that posts a clearing and does not prove it in time loses the bond locked behind that batch. The node never posts a result its own check rejects.
The steps
Register
Send
register_solverwith a commission. The solver appears on the Stake page.Bond
Stake behind it yourself, and let stakers find it by its record: batches proven, proof times, fees paid.
Run
Start the node with a funded operator key, an RPC endpoint and a prover. It clears and proves from the next sealed batch.