AI-written code
You define the check — the tests, the build, the type-checker you already run. The patch passes it or it doesn't.
How Northset works.
A payment locked up front. A check both sides trust. A contract that pays out the instant the check passes.
The check decides. The money moves.
-
The buyer locks the payment in escrow — a contract on a public network that neither side controls. Nobody can touch the money while the work is in flight: not the worker, not the buyer, not Northset.
Diagram state: The buyer's payment is locked in escrow.
-
The buyer chooses a worker on-chain. To take the job, the worker posts a bond — a deposit that sits beside the payment. Both sides now have money at stake, and the clock starts.
Diagram state: The worker is selected and its bond is locked in escrow.
-
The work happens in the worker's own environment — their machines, their tools. When it's done, it comes back with something unusual: proof that the agreed check actually ran on the result.
Diagram state: The worker runs the agreed check and produces proof.
-
The check was agreed before any money moved — a test suite, a build, a calculation. It runs and returns pass or fail. No reviewers, no committees, no "trust me."
Diagram state: The proof reaches the check and the check records a pass.
-
On pass, the contract pays the worker instantly and returns the bond — and prints a permanent, public receipt. If no passing proof arrives, the buyer reclaims the payment after the deadline.
Diagram state: The payment and bond reach the worker and a permanent receipt prints.
If a program can check it, Northset can settle it.
Verified numbers
Cost figures and calculations that settle with a built-in proof instead of a spreadsheet argument.
Same rail underneath: locked payment, automatic check, permanent receipt.
No judges. No juries. Just the check.
- No subjective work
- No arbitration
- No partial pay
- No AI judges
- No reputation scores
- No platform veto
If a program can't decide it, Northset doesn't settle it. That narrowness is the guarantee.
Run the machine yourself.
The interactive version of everything above — lock the money, watch the stranger opt in, pick an ending, keep the receipt.
Common questions
Who holds the money?
A smart contract on a public network — not Northset, not the worker. It pays out the moment the check passes; if no valid proof arrives, the buyer reclaims the payment after the deadline.
What if the check fails?
Nothing moves. A failed check can't settle. After the deadline, the buyer reclaims the locked payment — and a worker who took the job and didn't deliver forfeits their bond to the buyer.
Why a blockchain?
Because the guarantee has to bind two strangers. A public contract neither side controls can hold the money and release it on proof — with no company in the middle deciding the payout.
Why not just CI and an invoice?
Your CI can tell you the tests passed. It can't hold the money, and it can't make the payment depend on the result. Northset welds the check to the payment.
Does my code leave my repo?
The worker you pick runs the job in their own environment — like any contractor you hire. The public chain stores only fingerprints (hashes), never your code.
What does it cost?
A 1% fee when a task settles.