Protocol
Architecture
VOXX separates expensive execution from bounded settlement. Workers compute off-chain; EVM contracts record commitments, call approved verifiers, and conserve escrowed value.
Four contracts
JobRegistry | Creates canonical job commitments, snapshots economic terms, calls the selected verifier, records one accepted result, and exposes deadline refunds. |
|---|---|
EscrowVault | Locks one native-asset balance per job. Only its one-time-bound registry can distribute or refund funds. Recipients withdraw from pull balances. |
VerifierRegistry | Stores non-overwritable verifier IDs, adapter addresses, versions, status, and metadata. Administrative deactivation can halt compromised adapters. |
ProtocolConfig | Controls prospective fee, treasury, reward limits, duration limits, input size, and job admission. The fee is capped at 10% in v0.1. |
Job state machine
A job cannot settle or refund twice. Its requester, fee recipient, program, verifier, input commitment, reward, fee, and deadline remain fixed after creation.
Data and value path
The settlement layer does not interpret arbitrary proof bytes. It passes the job-bound statement to the chosen adapter and acts only on the adapter's boolean result.
Administration and upgrades
v0.1 uses OpenZeppelin Ownable administration for verifier registration and prospective configuration. The contracts are deliberately non-upgradeable. A production release should use delayed multisignature control, publish reproducible bytecode, deploy versioned contracts, and require explicit migration rather than silently changing live job semantics.
Asset boundary
Native-asset escrow is implemented. $VOXX settlement is a target extension requiring an allowlisted ERC-20 vault and a separately reviewed token contract. Neither asset changes the host chain's consensus or gas requirements.