Settlement
Multi-provider jobs settle through a reputation-weighted BFT cohort, then the Solana program re-verifies proofs against stored state — so a compromised off-chain cohort cannot override on-chain truth.
Heavy compute and proving run off-chain; trust-critical state settles on Solana. The design rule: correctness never depends on an off-chain party staying honest.
How a job settles
- A job runs inside a TEE and emits a receipt.
- For multi-provider jobs, a reputation-weighted BFT cohort of validators agrees on the outcome.
- The Solana program re-verifies the proofs against stored state before settling payment.
That last step is the safety net: even if an off-chain cohort were compromised, it cannot override what the on-chain verifier accepts. Off-chain consensus proposes; the chain disposes.
Anchored, not trusted
| Layer | Runs where | Trusted? |
|---|---|---|
| Inference + proving | Off-chain (provider TEE) | No — output is proven |
| Cohort agreement | Off-chain (validators) | No — re-verified on-chain |
| Final verification + payment | Solana program | Yes — this is the anchor |
Sub-second verification
Verification is meant to be cheap: constant-size proofs verifiable in ~10 ms on a single CPU core, with on-chain verification staying under a second. Any laptop or phone can check an Omyra receipt.