Protocol
Security Model
VOXX is only as sound as its job specification, proof system, verifier adapter, settlement contracts, and host chain.
Research onlyv0.1 has not been independently audited and must not custody production value. The demonstration verifier is not suitable for public deployment.
Core invariants
- One job reaches at most one terminal state:
SettledorRefunded. - A vault distribution must equal the exact amount locked for that job.
- The fee and fee recipient do not change after job creation.
- Only the one-time-bound
JobRegistrycan mutate escrow accounting. - Verifier IDs cannot be overwritten after registration.
- Settlement binds the submitter as the reward beneficiary.
Threats and controls
| Copied proof | Bind the beneficiary and chain-specific job ID into the verifier statement. The demo payload remains publicly reproducible and is not a production defense. |
|---|---|
| Mutable verifier | Use content-derived IDs, reproducible bytecode, immutable adapters, and explicit version migration. v0.1 registration does not enforce these production rules. |
| Escrow reentrancy | Apply checks-effects-interactions, use pull withdrawals, and reject direct vault transfers. |
| Worker compromise | Use isolated runtimes, program allowlists, reward thresholds, simulation, restricted signers, and minimal wallet balances. |
| Administrative key loss | Move ownership from a deployer key to delayed multisignature control before a value-bearing pilot. |
| Unavailable data | Commit availability terms explicitly. Proof of execution alone does not guarantee that inputs or outputs remain retrievable. |
Trust boundaries
The host chain is trusted for ordering, finality, contract execution, and gas accounting. Each verifier is trusted only for the statement encoded by that adapter. Requesters remain responsible for selecting correct programs, inputs, and verifiers. Workers remain responsible for protecting their signing keys and deciding whether a job is economically rational.
Production release gates
- Replace the transparent demo with an audited production proof backend.
- Add fuzzing, stateful invariants, fork tests, failure injection, and reproducible test vectors.
- Commission independent reviews of contracts, worker software, circuits, and deployment tooling.
- Publish verified bytecode, canonical addresses, verifier keys, and immutable release manifests.
- Transfer administration to a documented delayed policy and test emergency procedures.
- Run a capped pilot before raising value limits or admitting additional assets.
Reporting
Review the repository's security policy before reporting a vulnerability. Do not disclose an exploitable issue in a public discussion thread.