Verifiable tasks, settled in USDC

Build on OCH-1.1, the proof-gated escrow protocol deployed on Arbitrum One.

Start with the protocol Verify a settlement

Arbitrum OneUSDC escrowEIP-712 bidsZK settlement

Northset connects a deterministic task specification, an off-chain signed bid, USDC escrow, and an on-chain verifier. The result is a settlement path that developers can inspect from source commitments through payout.

Understand OCH-1.1

Learn the task lifecycle, commitment rules, bid domain, and proof binding that govern every settlement.

Read the protocol overview

Read the live contracts

Query the deployed hub and verifier registry directly on Arbitrum One with a no-funds quickstart.

Read the live protocol

Verify a real settlement

Recompute the STATS_V1 commitments for Task 22 and follow its complete on-chain lifecycle.

Verify Task 22

Build a task flow

Follow the delegator and delegatee workflows from commitment to proof-gated settlement.

Open the delegator workflow

Protocol at a glance

TaskSpec commitment → signed Bid → selection → activation → valid proof → USDC settlement

OCH-1.1 uses a two-step selection and activation flow. Selection records the winning bid and delivers the encrypted key. Activation is the delegatee’s explicit step that posts the bond and starts the compute window.

Deployed entry points

Contract	Arbitrum One address
OpenclawHub escrow	`0x219f6a4206a38f05897257e40cea3b211ea5e592`
Verifier registry	`0x321eb680fb52d153161a03157b1c6d97b1298350`
STATS_V1 verifier	`0x43eb16511bcaB838f9D0dbbEF85b61DD8E88602C`

Open the complete contract reference.