Verifiable Execution (zkVM)

Orion keeps rebalancing scalable without giving up verifiability. The protocol uses a zero-knowledge virtual machine (zkVM), powered by Succinct, so that heavy order-generation logic runs offchain while the chain only verifies a small proof. The result: many vaults and assets can be rebalanced in one epoch with constant verification cost.

How It Fits in the Flow

1. The Liquidity Orchestrator reads prices from oracles and commits the current protocol state onchain (a compact commitment, not the full state).
2. An offchain keeper runs the order-generation logic inside a zkVM circuit. The circuit computes both an input commitment (from the committed state and prices) and an output commitment (from the generated orders).
3. The zkVM produces a zero-knowledge proof that attests: “the output commitment is the correct result of running the order-generation logic on the input commitment.” The proof does not take the raw orders as input, only the commitments, so proof size and verification cost stay constant even as the number of vaults and orders grows.
4. The state machine that drives this process is fault tolerant: if a step fails, the system can recover and retry without corrupting state.
5. Onchain, the Liquidity Orchestrator receives the proof plus the actual order payload. It validates the proof using the verification key, the proof, and the committed state (checking that the output commitment matches). Only after validation does it use the payload to move liquidity and update vault accounting.

Why This Matters for Managers

• Verifiability: Every rebalance is cryptographically verified onchain; the chain never trusts the keeper’s output without a valid proof.
• Scalability: Expensive computation stays offchain; the chain only verifies a small proof, so cost does not grow with the number of vaults or orders.
• Safety: Validation (verification key, proof, and state) happens before any liquidity movement or accounting change, so invalid or tampered orders are never applied.