Live proof · Arbitrum One
Northset v1.1 on Arbitrum One
Every address and transaction below is independently verifiable on Arbiscan.
§ 01The receipt
A real task, paid by proof
Deployments prove existence. Completed settlements prove utility. The receipt here is the canonical one: controlled Task #6 on the native V2 repo-patch verifier — our team drove the run, the contracts and the USDC were real, and the settlement transaction is public.
NORTHSET · ARBITRUM ONE
PROOF-OF-PASS RECEIPT
- TASK
- #6
- LANE
- REPO_PATCH_HARNESS_V2
- SETTLED
- MODE
- CONTROLLED EVIDENCE RUN
- createTask USDC escrowed by buyer
- selectBid worker chosen on-chain
- activateTask worker bonds, clock starts
- submitResult proof verified, paid out
RESULT
verify exit code 0 · payout released
bond returned · fee 100 bps
SETTLEMENT TX 0x50fc695c…4da2f5
THE RECEIPT IS PERMANENT
Controlled Task #6: a native REPO_PATCH_HARNESS_V2 settlement with activation-bound public values and a public settlement transaction — not a production, marketplace, or self-serve code-change claim. Each tracked settlement can produce a buyer-safe receipt: one task, one check, one settlement record.
What it binds
Repo, base commit, patch hash, check command, verifier, task ID, USDC amount, settlement transaction.
Who it's for
The reviewer, the budget owner, the auditor — anyone who needs to know what was paid for and why, without trusting a dashboard.
The first
The historical first: Task #3, the first live repo-patch settlement (REPO_PATCH_HARNESS_V1, settled 2026-04-20, 100 USDC Metrica pilot). It proved live settlement; Task #6 is the canonical receipt for the current product. Task #3 settlement tx ↗
§ 02Deployed contracts
Live addresses on Arbitrum One
Core protocol contracts. Click any Arbiscan link to inspect bytecode and history.
Verifier registry
verifier families + codehashes
0x321eb680fb52d153161a03157b1c6d97b1298350 REPO_PATCH_V2 verifier
successor repo-patch verifier
0xa84698181a18c038dbd0ca08bb77b2404b194fc5 Disclosure
The verified contract symbol on Arbiscan is OpenclawHubEscrowV1_1 — preserved from the pre-rename deploy. Same hub, same Northset v1.1.
§ 03Verifier families
The deterministic programs that decide settlement
The deterministic programs that decide settlement. The hub snapshots the verifier ID and codehash at task creation, so later registry changes cannot redirect open tasks.
REPO_PATCH_HARNESS_V1
Proof-of-Pass Escrow for AI-written code. Patch applies cleanly to the declared base, the declared check command runs, the result is a pass.
- Verifier ID
- 0xeeeed6e9708c5f63fa387bc935917d14f4b0ee5a88141cdace4bd91514da0298
REPO_PATCH_HARNESS_V2
Successor repo-patch verifier with allowlist attestation, backing newer repo-patch lanes.
- Verifier ID
- 0xede169ce377c38b5721f5e18f85695df8630a4e68ee32e559a3d2815d351584c
STATS_V1
The statistics lane: a deterministic summary over one bounded, integerized cost batch.
- Verifier ID
- 0x87964240a746236cc99fb5d3ff344e5110b6429980582b953c2de786a74347b4
§ 04Governance
Multisig wallets that hold protocol authority
Two Safe multisigs. Owner Safe is the registry admin. Treasury Safe receives the protocol fee.
§ 05Global economics
Fee and minimum bond
Protocol-wide parameters. Fee in basis points is snapshotted at selection — later fee changes cannot retroactively alter open tasks. Minimum bond enforced at activation.
Global fee
100 bps
1.00% — snapshotted at selection
Global minimum bond
10 USDC
enforced at activation
§ 06Deploy transactions
How each contract reached main
Transaction hashes that created each contract. Arbiscan preserves the deploy receipt and the verified source.
Verifier registry deploy
0xb84b12ed61e978d5c34823243251c27bba779987b321cf671eb21bef6a35f92a STATS_V1 verifier deploy
0xb659a1b06255ec9b12abbc2d179bb6d5a986b68936e734531c78161d8bf39fa8 This page is the human-readable view. The deployment manifest has the full machine-readable bill of materials.