Glossary

Activation: The selected delegatee’s on-chain acceptance of a task. Activation posts the bond and starts the compute window.

Bid: An EIP-712 signed offer from a delegatee. It binds the task and verifier commitments, reward, bond, compute window, validity deadline, nonce, and salt.

Bond: USDC posted by the delegatee at activation. The hub returns it on valid completion and transfers it to the creator on timeout.

Creator (delegator): The address that creates a task, funds its reward escrow, and selects a bid.

Delegatee: The address that signs a bid, activates after selection, and submits the proof-bound result.

DCT: A Delegation Capability Token that grants scoped, time-bounded access to an off-chain resource. DCTs do not control on-chain settlement.

DID: A decentralized identifier used off-chain for participants. OCH-1.1 uses the canonical form did:pkh:eip155:<chainId>:<0xAddress>.

Encrypted key: The bounded byte payload emitted at selection for key delivery to the chosen delegatee.

Escrowed reward: The USDC held by the hub for a task. After selection it equals the chosen bid reward.

Input hash: The bytes32 commitment to the verifier program’s input.

Microunit: The integer unit used for USDC amounts. One USDC equals 1_000_000 microunits.

Output hash: The non-zero bytes32 commitment to a completed task’s output. The hub records it after proof verification.

Public values: The static ABI-encoded values bound into a proof. They begin with taskId, inputHash, and outputHash.

Specification hash (specHash): The raw bytes32 Keccak-256 hash of the RFC 8785 canonical JSON bytes of a TaskSpec.

TaskSpec: The off-chain JSON object that defines an objectively verifiable task. Its canonical JSON contains no floating-point values.

Verifier contract: The on-chain wrapper that checks a proof and its exact public values for one verifier program.

Verifier ID: The bytes32 identifier derived as keccak256(bytes(verifierFamilyName)) for a family documented in the OCH-1.1 portfolio.

Verifier program: The deterministic computation whose accepted execution is established by a valid proof.

Verifier registry: The on-chain mapping from a verifier ID to its wrapper address and active state. The hub snapshots the selected wrapper when a task is created.