– NEAR
– tUSDC
Escrow · AI auditor · NEAR
The client locks NEAR or a stablecoin in a contract. When the freelancer hands in the site (gas-free), two independent AI auditors open it in throwaway sandboxes and check it against the agreed criteria. Both must agree. After a short challenge window the contract pays the freelancer. The auditors' keys can't send money anywhere else, and one hijacked auditor can't pay out alone.
– NEAR
– tUSDC
0 locked
– NEAR
– tUSDC
Hand in a version of the site gas paid by the relayer
| Check | Needed | Got |
|---|
Evidence report · sha256 stored on chain
Assume auditor A is fully compromised and the freelancer colludes with it. Each line below is a real signed transaction on testnet using A's real key.
Pass or fail is plain code comparing measured scores with the criteria the client locked in. The language model only writes the note.
Each audit runs in a fresh, unprivileged container with no keys. Hostile scripts and hidden instructions on the site are recorded as findings.
The contract pays only the job's freelancer, only that milestone's amount. Each auditor holds a function-call key that can call report/release and nothing else. The vault has no keys at all: its code can't be changed.
Two independent auditors must both pass a milestone, then the client has a challenge window to dispute before any money moves. One hijacked agent can't pay out.
The note is written by NEAR AI Cloud inside a TEE. Its signature is checked against a fresh attestation and the proof's hash is stored on chain next to the verdict.
Pay in NEAR or a NEP-141 stablecoin. The freelancer submits gas-free through a meta-transaction relayer that only pays for submit. Accountants get a CSV.