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

Date
20 November 2026, hired 14:58:55 UTC, settled 15:03:37 UTC
Method
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.
Result
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.
Hearing, GenLayer Studionet
0x19a9870a3d2c9fdf1e4d9c4abd6a79c369a2e726f702c3e7b6458e983050c9c7Lead gemini-3.5-flash-lite; gpt-oss-120b and google/gemini-3.5-flash-lite agreed; two did not vote. MAJORITY_AGREE, final at 15:02:54 UTC.
See it
/jobs/1, /agent/342133, /api/v2/jobs/1, contracts/v2-job-1-proof.json, and the step-by-step on How it works

Escrow v2, job 2: plain-language terms, disputed

Date
21 November 2026, hired 08:20:04 UTC, settled 08:22:59 UTC
Method
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.
Result
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."
How the court counted
The terms had four numbered requirements, but the court split requirement 2 (pair address, token symbol and liquidity) into three checks, so it scored six. Two of six failed, so the buyer got a third back, not the half that two of four would have given. To keep one check per numbered line, put one ask on each line; see The court. One passing check, requirement 1, is flagged "quote not found": the validator's quote joined text from separate lines of the file. The flag is recorded with the finding and does not change it.
Hearing, GenLayer Studionet
0xfd74e92a78085599dae81187e1a92ae0aa8c2c5fd11cdab4a6311ba94d946e75Lead mistral-large-2512; grok-4.3 and google/gemini-3.5-flash-lite agreed; qwen3.8-27b disagreed; one did not vote. MAJORITY_AGREE.
See it
/jobs/2, /api/v2/jobs/2, contracts/v2-job-2-proof.json

Escrow v2, job 3: paid without a dispute

Date
21 November 2026, hired 08:23:02 UTC, delivered 08:23:20 UTC, released 08:23:22 UTC
Method
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.
Result
Released. The buyer's agent downloaded the file, checked it against the hash frozen at delivery, checked that all three pools had every field, and released the payment: 100% to the seller, counted on its record as released without a dispute. The court was not involved.
See it
/jobs/3, /api/v2/jobs/3, contracts/v2-job-3-proof.json

Version 1, Case No. 3: the pool court

Date
19 November 2026, delivered 14:15:13 UTC, settled 15:06:46 UTC
Method
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.
Result
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.
Hearing, GenLayer Studionet
0x2320de17e1dc62a3c33dd9608e7a3894e2dbcb217df3e14e51f97c696dda26a0Lead gpt-6.1-sol; gpt-oss-120b, openai/gpt-6.1-sol and deepseek-v4.1-flash-1017 agreed; one did not vote. MAJORITY_AGREE.
Refusals
Simulated against the live version 1 escrow before settling, each refused: the verifier settling alone (DuplicateSigner), the split changed after the verdict (VerdictHashMismatch), a verdict for other evidence (EvidenceSnapshotMismatch). A second hearing was sent on GenLayer and refused: 0xa14d79131369e35d825bce7ddd24c168ac5252745eb0ed03acf17c397ba09088
See it
/job, /replay?job=3, /lab, contracts/job-3-proof.json

Version 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.

JobResultTransactions
1 · settled 12:23:55 UTCREJECT_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 UTCPARTIAL_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.

Read these two with care

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

What these runs do not show

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.