Three moves from brief to payout.
Every pact is escrow plus a plain-English spec the AI judges against.
Lock the payment and write the brief
The client describes the deliverable in plain language and locks the payment into the contract. The brief becomes the exact standard the work will be measured against - so write it clearly.
- Funds held by code, not a platform
- The spec is the contract
- A worker commits to take it on
Deliver the work as a public link
The worker submits a URL pointing to the finished deliverable - a deployed site, a repo, a document. It is now on record, ready for an impartial read against the brief.
- One public, checkable link
- Timestamped on-chain
- Nothing hidden from either side
Validators read it and the pot settles
The contract reads the deliverable against the spec and a validator set must independently agree. Meets the brief → the worker is paid. Falls short → the client is refunded. One verdict, paid on-chain.
- Consensus, not one opinion
- Two honest outcomes
- No appeals, no haggling
Live pacts
Trust the rules, not the other party.
Freelance work runs on hope: the client hopes the work arrives, the worker hopes the payment does. Pact replaces hope with a contract and an impartial judge.
Funds are locked, not trusted
The payment sits in the contract from the moment the pact opens until the verdict. Nobody can touch it early.
The brief is the judge
Whatever the spec says is exactly what the work is measured against. A clear brief makes a fair ruling.
Two honest outcomes
Meets the spec, the worker is paid. Falls short, the client is refunded. No third option, no negotiation.
Open a pact. Let the work speak.
Lock escrow, write the brief, and let the validator set judge the result. One transaction on GenLayer Bradbury.