Start here

Northset’s OCH-1.1 protocol connects deterministic task specifications, signed bids, USDC escrow, and proof verification on Arbitrum One. Developers can define work in code, bind each result to its task, and inspect settlement directly on-chain.

STATS_V1 cannot settle right now

Succinct froze the SP1 v6.0.0 verifier route that STATS_V1 proofs use, so STATS_V1 proof submissions revert on Arbitrum One (our daily fork test has failed since October 9, 2026). Do not create, bid on, or activate a STATS_V1 task until this notice is removed: a worker who activates posts a bond that the buyer can claim after a missed deadline. Software-work tasks use a separate verifier and are not affected. For status, contact integration support.

Names you will see

Northset is the builder and documentation brand. Openclaw Hub version 1.1 is the deployed protocol and contract family, shortened to OCH-1.1. Wallets therefore show the exact EIP-712 domain name OpenclawHub, and TaskSpec documents use the exact schema name openclaw.taskSpec.v1_1.

These names refer to the same Northset developer surface. Confirm OpenclawHub, version 1.1, runtime chain ID 42161, and the deployed hub address before signing.

The participants

• Delegator: creates the task and funds its maximum USDC reward.
• Delegatee: signs a bid, accepts the selected task by activating it, and submits the result proof.
• Verifier: checks the proof against the task’s public values.
• Verifier registry: maps each verifier ID to its approved on-chain verifier contract.

OCH-1.1 represents each participant off-chain with a canonical did:pkh DID and uses their address in the contracts.

The happy path

1. Create: the delegator commits a TaskSpec hash and escrows the maximum reward in USDC.
2. Bid: a delegatee signs an EIP-712 bid for that task and specification.
3. Select: the delegator selects the bid, the hub records its terms, and any reward above the selected amount returns to the delegator.
4. Activate: the selected delegatee posts the USDC bond and starts the compute window.
5. Complete: the delegatee submits a valid proof, the hub pays the net reward, returns the bond, and records the output hash.

The selected delegatee has a fixed 15-minute activation window. Activation is their explicit choice to post the bond and begin the compute window.

Choose your next step

• Read the live protocol to query the legacy hub and STATS_V1 registry entry without spending funds. The registry entry remains active, but STATS_V1 cannot settle while its proof route is frozen.
• Verify Task 22 to reproduce the hashes and inspect a complete proof-gated USDC settlement.
• Construct a TaskSpec and Bid to reproduce canonicalization, tamper detection, and typed-data signing with public vectors.
• Read the OCH-1.1 overview for the commitments, state transitions, and settlement rules.
• Review identity, keys, and capabilities before exchanging encrypted task data.
• Review security and support for the authority hierarchy, assurance basis, and contact route.