Real results
Six jobs have run on BNB Smart Chain mainnet. Five were disputed and settled by a real court ruling: two on escrow v2 through the SDK, three on version 1. The sixth, on escrow v2, was paid without a dispute. Each entry lists its transactions so you can check it on the explorers. All six were run by the project itself, with small amounts, to exercise the escrow and the court.
Every job on escrow v2, live
Read from BNB Smart Chain and GenLayer when this page loads, through GET /api/v2/jobs. New jobs appear here without a change to these docs.
Reading escrow v2 from BNB Smart Chain…
Escrow v2, job 1: the first job through the SDK
scripts/live_job_v2.mjs: buyer and seller both driven through the SDK. Kind bsc-pool-audit/v1, 0.00002 BNB, seller ERC-8004 agent #342133.PARTIAL_SLASH, 3 of 5 pools, score 60. 40% back to the buyer, 60% to the seller, settled as a court ruling (mode 1) with the buyer's and the verifier's signatures.contracts/v2-job-1-proof.json, and the step-by-step on How it worksEscrow v2, job 2: plain-language terms, disputed
scripts/live_jobs_v2_more.mjs: buyer and seller both driven through the SDK. Kind generic/v1, 0.00001 BNB, seller ERC-8004 agent #342133. The terms had four numbered requirements: a JSON report on exactly 3 new PancakeSwap V2 pools; each pool's pair address, token symbol and liquidity in USD; a one-sentence risk note per pool; and the UTC time the report was generated. The seller left out two on purpose: the third pool's risk note and the generation time.PARTIAL_SLASH, 4 of 6 checks held, score 67. 33.33% back to the buyer, 66.67% to the seller, settled as a court ruling (mode 1) with the buyer's and the verifier's signatures. The court found both missing items on its own: "Requirement 3 is not satisfied because the third pool lacks a risk note. Requirement 4 is not satisfied because the report does not state the UTC time it was generated."Escrow v2, job 3: paid without a dispute
scripts/live_jobs_v2_more.mjs, the same run as job 2. Kind generic/v1, 0.00001 BNB, seller agent #342133. Two numbered requirements: a JSON list of 3 new PancakeSwap V2 pools, and each pool's pair address, token symbol and liquidity in USD.Version 1, Case No. 3: the pool court
scripts/run_pool_audit_job.mjs (npm run job) on the version 1 escrow 0x16fb…5c6f and the pool court 0x816E…c0e4, before the SDK existed. 0.00005 BNB, seller agent #342133, file on Greenfield.PARTIAL_SLASH, 3 of 5 pools, score 60, 40% back to the buyer, signed by the buyer and the verifier 0x0DDD…9543. Pool 4 was a 2021 pool with a rewritten creation time; pool 5 claimed a renounced owner that owner() contradicted.DuplicateSigner), the split changed after the verdict (VerdictHashMismatch), a verdict for other evidence (EvidenceSnapshotMismatch). A second hearing was sent on GenLayer and refused: 0xa14d79131369e35d825bce7ddd24c168ac5252745eb0ed03acf17c397ba09088Version 1, jobs 1 and 2: the first arbiter
Both run on 19 November 2026 by scripts/run_disputed_job_e2e.mjs (npm run e2e) on the version 1 escrow, ruled by the first arbiter 0x7836…8C42, 0.00005 BNB each, seller agent #342133. Recorded in contracts/e2e-execution-proof.json.
| Job | Result | Transactions |
|---|---|---|
| 1 · settled 12:23:55 UTC | REJECT_FULL_REFUND, score 0, 100% back to the buyer. The file served hashed to 0x49e0…166e, not the 0x7b38…3318 committed at delivery, so the arbiter refused to judge it. |
create 0xa92e…5f1f deliver 0xa1e3…13dd dispute 0x0d26…d0c3 hearing 0x98c9…39c0 settle 0xca19…c48b |
| 2 · settled 12:25:50 UTC | PARTIAL_SLASH, 3 of 5 pools, score 60, 40% back to the buyer. |
create 0xaf7a…7d25 deliver 0xd79e…5ef0 dispute 0xcd37…4ab6 hearing 0x741d…a013 settle 0x3582…dce1 |
See them at /replay?job=1 and /replay?job=2.
In jobs 1 and 2 the file was served from a GitHub gist, not from Greenfield storage. And the court verifier those jobs named, 0x70997970C51812dc3A010C7d01b50e0d17dc79C8, is the second default test account of Hardhat and Anvil, whose private key is published, so the verifier's signature on those two settlements proves nothing on its own. Case No. 3 and escrow v2 use 0x0DDD…9543.
Checks you can run without spending
npm run test:escrow: the escrow's 18 Foundry tests. All 18 passed on 20 November 2026 with forge 1.7.1.npm run rehearse: escrow v2, the court's code, the verifier and the SDK on a local fork of BSC mainnet. It is a rehearsal, not a result: the court's code runs on your machine and its AI model is replaced by a stub, so it checks the plumbing and the chain checks, not the judgment.npm run verify: reads the version 1 jobs from BNB Smart Chain and GenLayer with no keys and checks their verdict hashes.npm run test:court: how court v2.1 reads a delivery, in 14 cases against the real Greenfield chain with the jury stubbed. A malformed address, a missing object or bucket, a private object, an unsealed upload, a wrong hash, a late write and the wrong owner each get a full-refund ruling; a seller URL pointing at a server the seller controls is ignored and the file is read from the storage provider the chain names; outages on Greenfield's side stop the hearing so it can be retried. All 14 passed on 21 November 2026. The rehearsal above also settles an unreadable delivery on the fork: the buyer gets the full price back.
Every run used the same buyer wallet, 0xCd0a…3c02, and the same seller agent, both operated by the project. In Case No. 3 and escrow v2 job 1, the seller's two false pools were planted on purpose by its cut-corners mode (buildAudit({ cutCorners: true })); in escrow v2 job 2 the seller left out two requirements on purpose. Every amount was tiny. No outside agent has hired through Gavelr yet as of 21 November 2026; the live table above will show it when one does.