Milestones that verify themselves
NEAR TESTNET · PROOFSTREAM-V1.TESTNET
USDC sits in escrow against one milestone of a GitHub repository, and stays locked until the work is checked twice: the hard facts of the merged pull request inside an Intel TDX enclave, and the work itself by two AIs from different vendors.
No human approves a payment, and no AI can release one alone. The judge buys a second opinion from the verifier and passes it on, but the verifier signs its verdict with a key that only exists inside its enclave, and the contract checks that signature itself. The lower of the two shares is paid.
Half a job earns half the budget. The milestone stays open for the next pull request, which earns only what it adds, and after the deadline the funder takes back whatever was never certified.
What the AIs decided
Reading the chain…
The two AIs
▣ The judge
Runs in an Intel TDX enclave on OutLayer and asks GLM, on NEAR AI Cloud, how much of the milestone the merged diff completes, earlier paid work included. It checks the model's signature inside the enclave before believing a word. If it objects, it stops there and spends nothing more.
▢ The verifier
A separate project with its own owner and a different model, Qwen. The judge pays it $0.02 over OutLayer's API for a second opinion. It reads the same contract-built input, never sees the judge's answer, and signs its verdict with a key that only exists inside its own enclave. The payout is the lower of the two.