Commit · program 12 · round 0
No rule broke, but a protected account lost more than the program's threshold; re-run 109, 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 8wgFtZVk…, NEAR transaction: 8wgFtZVkottLAiR8a9MuuGhXUaSVJVjkwayZqzcSbkvx, opens an explorer in a new tab
The gap lane
Committed
Revealed · run 102 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 a489087abfe5…, receipt sha256: a489087abfe5e50bb8fc93a56824c1856682cca228cf1e817f7d4037b9db30b2. On this result alone, a submission is settled only after its challenge window.
Delivered in 4Kpd6eSc…, NEAR transaction: 4Kpd6eSchzG9ZzXavzFUYDwK7JKrcPH8ZZMr1p9Pwi7Q, opens an explorer in a new tab
antibody status --run 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 61Enclave verdict: no violation
Attested on NEAR
Gap claim recorded
Re-run requested at round 1's fix · run 109
Re-run at round 1's fix: violation of the “protected balances” rule
Re-run attested on NEAR · run 109
Promoted at round 1
Paid 0.01 wNEAR
Re-run requested at round 2's fix · run 114
Re-run at round 2's fix: no violation
Re-run attested on NEAR · run 114
Re-run requested at round 3's fix · run 119
Re-run at round 3's fix: no violation
Re-run attested on NEAR · run 119
Re-run requested at round 4's fix · run 125
Re-run at round 4's fix: no violation
Re-run attested on NEAR · run 125
Re-run requested at round 5's fix · run 130
Re-run at round 5's fix: no violation
Re-run attested on NEAR · run 130
Re-run requested at round 6's fix · run 135
Re-run at round 6's fix: no violation
Re-run attested on NEAR · run 135
Re-run requested at round 7's fix · run 140
Re-run at round 7's fix: no violation
Re-run attested on NEAR · run 140
Re-run requested at round 8's fix · run 149
Re-run at round 8's fix: no violation
Re-run attested on NEAR · run 149
Re-run requested at round 9's fix · run 156
Re-run at round 9's fix: no violation
Re-run attested on NEAR · run 156
Re-run requested at round 10's fix · run 166
Re-run at round 10's fix: no violation
Re-run attested on NEAR · run 166
Re-run requested at round 11's fix · run 171
Re-run at round 11's fix: no violation
Re-run attested on NEAR · run 171
Re-run requested at round 12's fix · run 192
Re-run at round 12's fix: no violation
Re-run attested on NEAR · run 192
Re-run requested at round 13's fix · run 204
Re-run at round 13's fix: no violation
Re-run attested on NEAR · run 204
Re-run requested at round 14's fix · run 214
Re-run at round 14's fix: no violation
Re-run attested on NEAR · run 214
Re-run requested at round 15's fix · run 219
Re-run at round 15's fix: no violation
Re-run attested on NEAR · run 219
antibody program read --api fetches.Holds if: near-antibody stores commitment bec7ad848a57… for commit 61
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 61jGuRYq…, NEAR transaction: 61jGuRYqa53LZUmBDTscDP2xUeFgLuBQVwjZCaiyvh3B, opens an explorer in a new tab
antibody tee check --request-id <the run's OutLayer request>outlayer-verify tx 4Kpd6eSchzG9ZzXavzFUYDwK7JKrcPH8ZZMr1p9Pwi7QHolds 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 102Program 12: its rules, escrow and rounds.