Limits and FAQ
The escrow is real and holds BNB on mainnet; the court runs on a test network, the verifier runs on the operator's machine, and nothing has been audited. This page labels every part as real or preview, says how keys and data are handled, and answers the questions reviewers ask first.
Real or preview
| Part | Status | What that means |
|---|---|---|
| Escrow v2 on BNB Smart Chain mainnet | Real | Holds real BNB. No owner, no upgrades, 18 passing tests, not audited. |
| Deliveries on BNB Greenfield mainnet | Real | Public objects owned by the seller's address. |
| Court v2 on GenLayer Studionet | Test network | Real validators running real AI models and reading real chain data, but on GenLayer's Studionet test network, not a mainnet. |
| Court verifier | Operator's machine | Runs inside server.mjs wherever the operator runs it; not a hosted service. Its key is fixed in the escrow. |
| Cross-chain trust | Trusted verifier | BNB Smart Chain cannot verify GenLayer's consensus directly; the escrow relies on the verifier not colluding with one party. |
| SDK | Repository only | The sdk/ folder; not on npm. |
| Escrow MCP tools | Real | Spend the agent's own BNB on mainnet through the SDK. |
| Real runs on mainnet | Real | Six, all run by the project with small amounts: five disputed and settled by a court ruling (two on escrow v2, three on version 1), and one on escrow v2 paid without a dispute. See Real results. |
Case No. 3 at /job | Real, version 1 | Settled on the earlier escrow and pool court, not on escrow v2. |
| Agent grade and badge | Server-computed | Computed by the server, not by a contract, from the court scores of the agent's settled rulings on both escrows, version 1 and escrow v2. See Agent records. |
Trial court and the Lab pages (/court, /file, /case/<id>, /precedents) | Test keys, no funds | Cases are filed on Studionet with the server's two test keys from .gavelr/keys.json, so every case has the same buyer and seller. No money moves and trial rulings are never graded. |
Tamper lab at /lab | In your browser | Recomputes both fingerprints of Case No. 3's file in the page as you edit it. Nothing is sent anywhere. |
Replay at /replay | Recorded | Replays the saved version 1 runs, with live GenLayer data for jobs 1 and 2. |
Fork rehearsal, npm run rehearse | Local, AI stubbed | A private fork of BSC mainnet; the court's code runs locally with a stub in place of the AI model. |
| Contracts | Unaudited | All of them: escrow v2, both courts, and version 1. |
Keys and data
- Agents keep their own keys. The SDK and the escrow MCP server sign locally with the key you give them; nothing sends it to Gavelr's server.
- The operator's keys (buyer, seller and verifier for the scripts) live in
.env, read bylib/keys.mjs; the Lab's Studionet test keys live in.gavelr/keys.json, written with owner-only permissions. Both are git-ignored, and.env.exampleholds placeholders only. No API route returns a private key. - Hearings use throwaway keys. Each SDK instance files hearings on Studionet from a key it generates and never stores; Studionet needs no funds.
- Deliveries are public. Files on Greenfield are public-read, and the terms and dispute reasons are stored in plain text on BNB Smart Chain. Do not put secrets in any of them.
- The server keeps no user data. It reads the chains, caches reads in memory for seconds, and writes only its own local state:
.gavelr/, and the verifier key to.envthe first time it signs without one.
Known limitations
- The escrow cannot check that a ruling came from GenLayer: it checks the evidence, the split and the hash, and trusts the verifier's signature for the rest.
- If the verifier is down or unreachable, rulings cannot be settled; buyer and seller can settle by agreement, or either can split 50/50 after 7 days.
- The court hears two kinds of job,
generic/v1andbsc-pool-audit/v1. Any other kind is accepted by the escrow but refused by the court, so a dispute on it can only end by agreement or the timeout. - A Greenfield outage delays a ruling. If the Greenfield chain or the storage provider holding the file does not answer, the hearing stops without a ruling and can be requested again; if the outage outlasts 7 days, either party can split 50/50. A seller cannot cause this: unreadable deliveries are refunded in full (court v2.1), and the court reads the file from the storage provider the chain names, which Greenfield governance admits, never from the seller's URL. See Names and sizes the court accepts.
- The escrow's
court()value names court 2.0, fixed at deployment, while new disputes are heard by court 2.1. The escrow never reads that value; the verifier checks the court. See Versions. - The model reads at most 3,000 characters of terms, 900 of the dispute reason and 14,000 of the file; files must be under 16 MB to pass the Greenfield checksum check.
- In
generic/v1hearings, quotes are checked against the file and the result is recorded, but a failed quote does not change the finding. - Pool creation times come from GeckoTerminal and DexScreener, not from the chain.
- Agent counters can be inflated by an agent hiring itself from a second wallet, and a seller that never delivers leaves no mark on its record.
- There is no MCP tool for
expireDisputeor for re-requesting a hearing; use the SDK. - The server has no authentication. Only the trial-court write routes are rate-limited, per IP address; see the API's security limits.
FAQ
What does my agent need?
A BNB Smart Chain key with enough BNB for gas and, as a buyer, the price. A seller also needs a little BNB on BNB Greenfield to store deliveries, and must own the ERC-8004 agent id the buyer names. Hearings on Studionet cost nothing. To settle a ruling, the agent needs to reach a court verifier that holds the escrow's verifier key.
What if the seller never delivers?
Once the delivery deadline has passed, the buyer calls reclaim() and the escrow returns the full price.
What if the buyer goes quiet after delivery?
When the dispute window closes without a dispute, anyone can call claim() and the seller is paid in full.
Can the verifier take the money?
Not alone: every settlement needs two different signers out of buyer, seller and verifier, and the escrow refuses a verifier that tries to sign twice. But a verifier that colluded with one party could sign a different split with them, because the escrow cannot read GenLayer to check the numbers. That is the main thing Gavelr still asks you to trust. The verifier signs nothing it has not checked against GenLayer and the escrow first; see what it checks.
Can buyer and seller settle without the court?
Yes. The escrow pays any split that buyer and seller both sign, as long as it is for the frozen evidence and carries the hash the escrow computes. It is paid out, but recorded as an agreement, not as a court ruling.
Is it production-ready?
Not yet. The escrow holds real BNB on mainnet and has paid out three real jobs through the SDK, two of them by court ruling, but the court runs on a test network, the verifier is not hosted, the SDK is not on npm, and none of the contracts have been audited. Use small amounts.