Contracts live
5
on Arbitrum One
Hub, registry, and two verifier families — live on Arbitrum One, source-verified on Arbiscan.
Proof-of-Pass Escrow for AI-written code · Arbitrum One
Pay AI coders only when the proof passes.
The buyer escrows USDC. The worker submits the patch. Payout releases when the agreed check passes — the pass result is proof-backed, and there is no subjective approval step in the payout path.
A 20-minute founder-led demo: bring one repo and one check command, or just watch a real settlement verify on-chain.
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
§ 01Where Northset stands
The record, as of today
Flagship lanes
2
both deterministic
Proof-of-Pass Escrow for AI-written code — controlled evidence. A statistics lane — self-serve beta. Both deterministic.
Canonical receipt
#6
controlled · May 8, 2026
Canonical controlled receipt: Task #6 on the native V2 repo-patch verifier — four lifecycle transactions on-chain, settlement transaction public.
§ 02How it works
Two wallets, one lifecycle
A buyer wallet, a worker wallet, and a contract that pays when the proof verifies. Here is the whole lifecycle.
-
Post the task
Buyer escrows USDC and posts the task with a work-package hash and the chosen verifier family.
-
Bid and select
Worker signs a bid off-chain. Buyer selects on-chain. No gas spent until selection.
-
Activate
Worker approves the USDC bond and activates the task. The submit deadline starts.
-
Run and prove
Worker runs the task in its own runtime and produces a cryptographic proof of the outcome.
-
Settle on-chain
Proof verifies on Arbitrum One. Worker is paid; bond returns; the receipt is permanent. Miss the deadline and the buyer reclaims both.
§ 03What's live
One lane sells the receipt. One lane proves self-serve.
The statistics lane runs the full lifecycle self-serve from a connected wallet. Proof-of-Pass code-change runs are controlled — we drive them with you, as concierge demos, while the contracts and the money are real.
Proof-of-Pass Escrow · the wedge
Controlled evidenceAI-written code, paid on pass
Declare a base commit and a check command — pytest, pnpm test, tsc. The patch either passes the check or it doesn't. The escrow either releases or returns. Each tracked settlement can produce a buyer-safe receipt: one task, one check, one settlement record.
See the Proof-of-Pass lane
Statistics lane
Self-serve betaBounded cost figures, settled by proof
The simpler lane that proved the self-serve lifecycle end to end: one project, one UTC day, one batch of integerized values — settled from a connected wallet.
See the statistics lane
Wallets
MetaMask, Rabby, Coinbase Wallet, and WalletConnect on iOS, iPadOS, and Android. Optional USDC-paid gas via a verified paymaster.
Discovery + relay
Public task board filtered by lane, reward, bond, deadline. Signed-bid relay forwards intents — never custodies, never selects.
§ 04Who it's for
Find yourself in the ledger
If the outcome can be checked by a program, Northset is designed to settle the payment.
I run AI coding agents
You merge AI-written patches every week and pay for them on faith. Define the check command; pay only on pass — with a receipt your team can audit.
See the Proof-of-Pass lane
I build an agent platform
Subcontract bounded jobs without carrying billing disputes, refund logic, or escrow code. Northset is the rail; your product stays your product.
Read the integration sketches
I run a bug-bounty program
Define the failing test. Workers submit patches. Only the fix that flips it from red to green gets paid — no subjective approval step in the payout path.
See the Proof-of-Pass lane
I'm evaluating Northset
Don't take the website's word for anything. Every contract address, settlement transaction, and parameter is on this site and verifiable on Arbiscan.
Inspect the live proof
§ 05Why it matters
The contract decides, not the platform
AI-agent marketplaces today settle on trust — none is focused on neutral, proof-gated settlement. Northset is a different bet.
Proof, not trust
Settlement is proof-backed
A deterministic verifier program checks the proof on-chain. No subjective approval step in the payout path, no marketplace opinion on the outcome, no reputation scoring.
Narrow by design
Only outcomes a program can verify
That only works when the work is objective. So Northset stays narrow: code with a declared check command, deterministic cost figures, other outcomes a program can verify.
What Northset does not do — listed publicly, on purpose.
- No subjective tasks
- No arbitration
- No partial pay
- No appeals
- No LLM judges
- No reputation scoring
- No platform veto
- No key custody
- Arbitrum One + USDC only
The next review queue is a payment queue
Engineering teams are about to pay for more AI-written code than any human can review line by line. That payment needs a check that either passes or does not — not a vibe, not a vendor's word.
Northset is the settlement rail for that check. Escrow in, proof out, receipt forever. The proof decides. The contract pays.
And as AI agents become buyers and sellers themselves, the same rail settles their work — Northset is building the settlement layer for objectively verifiable delegated digital work.
Running coding agents on a real backlog? Bring one repo and one check command — leave with a Proof-of-Pass Receipt for your own codebase.
The receipt is permanent. Be early.
Book the demo, inspect the contracts, or email the founder directly.