For: AI or compute networks, modular rollups, off-chain workloads

Problem

Decentralized compute today is costly, brittle, and easy to game. Most systems rely on ad-hoc coordinators, TEEs, or multisig committees that don’t provide chain-agnostic, slashing-enforced guarantees. Notable shortcomings include:

• High cost: bespoke committees/light clients per network, many sig verifications on-chain, custom relayers, repeated audits, and over-provisioned capacity drive unit economics up.
• Attack surface: forged results, equivocation (conflicting outputs), replay of old results, censorship/withholding, collusion among runners, coordinator DoS, key compromise, MEV/front-running on result publication, and TEE quote spoofing without on-chain anchoring.
• Weak incentives: runners often have little or no bonded stake; slashing paths are unclear or social, so bad behavior is cheap.
• Operational opacity & lock-in: logs and receipts are off-chain/opaque, integrations are bespoke per chain or vendor, and portability is poor.

Relay Solution

Relay turns each off chain computation, including container jobs, into a stake backed, verifiable receipt. These receipts can be checked on chain and, once approved, automatically trigger payments, unlocks, or workflow steps. There are no custom committees or heavy coordination, only clear proof that a job was done, with built in penalties for cheating or missed deadlines, lower costs at scale, and portability across any cloud or chain.

Some of the Relay advantages can be found below:

• Usage-based, provable billing: verifiable receipts include runtime/metrics so you can meter, invoice, and settle on-chain per job or per epoch.
• SLA enforcement: late, missing, or conflicting results are objectively slashable; clients get deterministic inclusion and dispute windows.
• Lower verification cost: aggregate many job receipts once per epoch → one on-chain verify for hundreds/thousands of tasks.
• Input/Output integrity: bind container image digest, parameters, data CIDs, and output/artifact hashes into the receipt to prevent tampering or replay.
• TEE or ZK, your choice: attach a TEE quote hash or a zk proof of execution when available; Relay’s stake guarantees still secure the base path.
• Multi-cloud portability: same receipt format and Verifier across L1s/rollups; run workers on any infra (K8s, bare-metal, cloud) without vendor lock-in.
• Fair marketplace for runners: bonded operators with reputations and slashing create credible supply; optional per-capability whitelists (GPU, RAM, CUDA).
• Composable callbacks: post-verify adapters can release escrow, mint compute credits, advance workflows, or trigger subsequent jobs.

How it Works