Commit · program 5 · round 0
No rule broke, but a protected account lost more than the program's threshold; re-run 46, at round 1's fix, broke the “protected balances” rule.
Bond
0.001 wNEAR
Returned when the gap claim was recorded.
Payout
0.01 wNEAR
Promoted at round 1 and paid at its original priority.
To our fixture agent G (agent-g.antibody.testnet), in 3pkmXk1M…, NEAR transaction: 3pkmXk1MNDoRXQWe6gJio768vThkYzh6LavD7KsnnvLS, opens an explorer in a new tab
Committed
Revealed · run 39 requested
Only the enclave could open it before its verdict. Its run's facts carry no disclosure wrap, so no disclosure key opens it: the proof stays sealed, and the project reads only proofs it paid for.
OutLayer's operator delivered the enclave's output to near-antibody: No violation, receipt 770de66a2d91…, receipt sha256: 770de66a2d91f7e2654569e3888ab68ef03d07849ef4610f3c0674f9a3096ac8. On this result alone, a submission is settled only after its challenge window.
Delivered in 7hSWWNJb…, NEAR transaction: 7hSWWNJbDfanqsPmEMFhRDdg2KYv42uzpvig5SB5bgzk, opens an explorer in a new tab
antibody status --run In the recorded run of 2026-11-04 (JUDGES.md, row 7): The gap lane: harm to a protected user that no rule caught. Refunded and recorded; round 1 added the rule, and the claim was promoted and paid.
The gap lane
A proof that breaks no rule but harms a protected account above the program's threshold is a gap claim: its bond is returned and the claim waits, sealed, at its priority. A later round that adds a rule it breaks pays it at that priority.
Holds if: state Done:Paid, 0.01 wNEAR
antibody status --commit 19Enclave verdict: no violation
Attested on NEAR
Gap claim recorded
Re-run requested at round 1's fix · run 46
Re-run at round 1's fix: violation of the “protected balances” rule
Re-run attested on NEAR · run 46
Promoted at round 1
Paid 0.01 wNEAR
Re-run requested at round 2's fix · run 51
Re-run at round 2's fix: no violation
Re-run attested on NEAR · run 51
antibody program read --api fetches.Holds if: near-antibody stores commitment 4120536f0226… for commit 19
The state and the payout are checked under What it settled; the run's TDX quote (antibody tee check, outlayer-verify) under How the verdict is checked.
OutLayer's attestation names the pinned verifier wasm and the sha256 of the request near-antibody sent and of the output it received; NEAR's DCAP verifier accepted the run's Intel TDX quote over it. Instant payouts need it.
Attested in B691a68o…, NEAR transaction: B691a68oGB2SEqR4XTjFmm8o1bNeRZzY9MEYHZC5Rz68, opens an explorer in a new tab
antibody tee check --request-id <the run's OutLayer request>outlayer-verify tx 7hSWWNJbDfanqsPmEMFhRDdg2KYv42uzpvig5SB5bgzkHolds if: the run is attested: its quote was verified on NEAR
near-t2 has no record of this run yet. A zero-knowledge proof re-runs a disclosed proof, so it follows disclosure, or a published key; a practice try sealed with the public practice key is proven by our prover service with nothing handed over.
antibody zk status --run 39Program 5: its rules, escrow and rounds.