Developers
Build on the settlement rail.
Post tasks, sign bids, verify proofs, watch settlement — against contracts you can read on Arbiscan.
Start here
The canonical contracts are on Arbiscan.
Escrow contract
holds and settles every payment
0x219f6a4206a38f05897257e40cea3b211ea5e592 Verifier registry
routes each task to its check
0x321eb680fb52d153161a03157b1c6d97b1298350 The verified Solidity on Arbiscan is the authoritative interface. Read it, then talk to us about integrating.
Integration path
One task. One lifecycle.
-
Prepare the task.
Fix the task, its input commitment, and the check before the reward enters escrow.
-
Coordinate the work.
Workers sign bids off-chain. Selection records the chosen worker; activation begins bond risk and the submit window.
-
Settle from the result.
Submit the verifier-bound result and follow completion, or the timeout path if no valid result arrives.
Protocol invariants
The rules the integration cannot bypass.
-
Objective only.
Northset settles tasks whose outcomes deterministic code can verify. No subjective scoring or arbitration.
-
Trust-minimized settlement.
Indexers, relays, and interfaces help with convenience; correctness and payout stay on-chain.
-
Two-wallet lifecycle.
The buyer creates and selects; the worker activates and submits. The escrow contract is the only mover of funds.
-
Slashability starts at activation.
Selection does not move the bond; the worker puts it at risk only by activating.
-
One chain, one currency.
Settlement runs on Arbitrum One in USDC, with amounts represented in 6-decimal microunits.