Verifiable tasks, settled in USDC

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.

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.

Available now

Capability	Live status
Create and settle new software-work tasks	SOFTWARE_WORK_WASM_V1 on the software-work hub
Escrow rewards and bonds	Native USDC with 6-decimal integer amounts
Select off-chain EIP-712 bids	Supported by the deployed hub
Verify deterministic statistics	STATS_V1 remains active in the legacy registry; its proofs cannot settle while the SP1 v6.0.0 route is frozen (see the notice above)
Inspect state and receipts	Directly available from Arbitrum One RPC and logs

The deployed contracts and chain logs are the settlement authority. This site, SDKs, indexers, and relays help developers integrate; if a convenience surface differs from direct chain state, direct chain state wins.

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

Construct a TaskSpec and Bid

Reproduce a canonical TaskSpec hash, detect a changed commitment, and verify an exact EIP-712 fixture.

Construct a TaskSpec and Bid

Protocol at a glance

OPEN -> SELECTED -> ACTIVE -> COMPLETED
OPEN -> CANCELLED
SELECTED -> OPEN
ACTIVE -> TIMED_OUT

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

The software-work hub settles new software-work tasks through SOFTWARE_WORK_WASM_V1 and the direct SP1 v6.1.0 verifier. The legacy hub settled the earlier receipts, including task 22 and the May 8 receipt. STATS_V1 cannot settle while Succinct’s SP1 v6.0.0 route is frozen, since 2026-10-09; both legacy repo-patch routes are inactive. These statuses were checked at Arbitrum One block 515499563 on 2026-10-16.

Contract	Arbitrum One address
Software-work hub	0x99d42927268cDC18aA31CDd97588f53dFCa12Aa0
Software-work verifier registry	0xffF65E562e6c7f20982903aC85D06847e7Aa7E6A
SOFTWARE_WORK_WASM_V1 wrapper	0x42bCacb2709dA2fDA52a49b651A890F96a8AB438
Direct SP1 v6.1.0 verifier	0x082de66Fd00aBBD0d9bD24fAEe4A4a91D9E6D22F
Legacy hub: earlier receipts	0x219f6a4206A38f05897257e40ceA3B211eA5e592
Legacy verifier registry	0x321Eb680Fb52d153161a03157B1C6D97b1298350
STATS_V1 verifier: cannot settle	0x43eb16511bcaB838f9D0dbbEF85b61DD8E88602C

Open the complete contract reference.