Testnet: tokens have no value, and the vulnerable contracts are our own test fixtures. Limits

Run 117 · re-run · No violation · Attested on NEAR · Antibody

Run · re-run · program 12

Run 117

A re-run of commit 56's proof at round 3's code and rules: it breaks nothing, so the fix stops it.

No violationAttested on NEAR

What the enclave answered

The run as near-antibody records it: every hash below is checkable against NEAR.

Mode: rerun
A re-run of a paid proof, a duplicate or a gap claim at a newer round's code and rules.
Kind: No violation
Keys: none: at this round's code it breaks no rule
Impact: not published for a re-run
A re-run runs the project's fix against a proof it may not have paid for: its facts name only the keys that still break, never the impact or the harm.
Level: Attested on NEAR
Receipt sha256: c85cc0f22660a856…, receipt sha256: c85cc0f22660a85668ef7701d4128334d6ba915824cc61f175a8281e964adcda
Request sha256: 4bf600ad7169d848…, request sha256: 4bf600ad7169d848c29b5d70801bf4a731bfbdeff7207384d9222c144f797e24
The SHA-256 of the input near-antibody sent the enclave: its result and its attestation bind to the same bytes.
Output sha256: 71076cfd90bb6836…, output sha256: 71076cfd90bb68369b1ce34430db6ffca938c2ab2afb175d9c79d5cb41a77711
The SHA-256 of the facts near-antibody received: the TDX quote binds it.
Mode extras: none
Started: 2026-11-08 17:51:07 UTC665sY8Ez…, NEAR transaction: 665sY8Ez8pYnGJ1jGYaQcHaNGJ8jdkiDkaDGFRffiy3G, opens an explorer in a new tab
Answered: 2026-11-08 17:51:21 UTC14 s after it was requested665sY8Ez…, NEAR transaction: 665sY8Ez8pYnGJ1jGYaQcHaNGJ8jdkiDkaDGFRffiy3G, opens an explorer in a new tab
Commit: Commit 56
Program: Program 12round 3
Paid for by: keeper.antibody.testnet, account: keeper.antibody.testnet our account

No violationno rule broken

receipt c85cc0f22660…

Timeline

Every step is a NEAR transaction, timed by block from commit 56's block.

0.0 s (the commit's block)
Committed
A sealed proof and a 0.001 wNEAR bond, by our fixture agent B (agent-b.antibody.testnet). Nobody, the project included, can read it before its verdict.
FesPHtSz…, NEAR transaction: FesPHtSzKdsh88To1qxE1YB2Lo3huDwYv1GhGGXDhB5N, opens an explorer in a new tab2026-11-0817:09:24 UTC · block 276,804,416
+41.7 min after the commit's block
Re-run requested at round 3's fix · run 117
At a proposed fix, the keeper re-runs every paid proof (the release gate holds only if all of them fail against it) and every duplicate and gap claim (the fix may promote them).
665sY8Ez…, NEAR transaction: 665sY8Ez8pYnGJ1jGYaQcHaNGJ8jdkiDkaDGFRffiy3G, opens an explorer in a new tab

How it is checked

Three levels, each a check you can run yourself. The first two decide payouts; the zero-knowledge proof sits beside them.

Enclave verdictreached

What the enclave answered

OutLayer's operator delivered the enclave's output to near-antibody: No violation, receipt c85cc0f22660…, receipt sha256: c85cc0f22660a85668ef7701d4128334d6ba915824cc61f175a8281e964adcda. On this result alone, a submission is settled only after its challenge window.

Delivered in 665sY8Ez…, NEAR transaction: 665sY8Ez8pYnGJ1jGYaQcHaNGJ8jdkiDkaDGFRffiy3G, opens an explorer in a new tab

Check it yourself

antibody status --run 117

The raw record

Exactly what the API read from near-antibody's get_run view, for your own tools.

The run as near-antibody stores it (JSON)

get_run {"run_id": 117}

{
  "commit": 56,
  "id": 117,
  "mode": "rerun",
  "outcome": {
    "Answered": {
      "at": 1794160281,
      "facts": {
        "extra": "None",
        "impact_usd_micro": "0",
        "keys": [],
        "kind": "NoViolation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "c85cc0f22660a85668ef7701d4128334d6ba915824cc61f175a8281e964adcda"
      },
      "output_sha256": "71076cfd90bb68369b1ce34430db6ffca938c2ab2afb175d9c79d5cb41a77711",
      "tier": "T1"
    }
  },
  "payer": "keeper.antibody.testnet",
  "program": 12,
  "request_sha256": "4bf600ad7169d848c29b5d70801bf4a731bfbdeff7207384d9222c144f797e24",
  "round": 3,
  "signer": "keeper.antibody.testnet",
  "started_at": 1794160267
}

Attested on NEARreached

Its Intel TDX quote, verified on NEAR

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. A re-run's result counts only once its run is attested on NEAR.

Attested in Fzoijryz…, NEAR transaction: FzoijryzgUhe6WwRtBMBQTkHpRyGshLyFJW2EhHxxnrg, opens an explorer in a new tab

Check it yourself

tx 665sY8Ez8p… · NEAR archival RPC

antibody tee check --request-id <the run's OutLayer request>

outlayer-verify tx 665sY8Ez8pYnGJ1jGYaQcHaNGJ8jdkiDkaDGFRffiy3G

view bounty.antibody.testnet.get_run({"run_id":117})

Holds if: the run is attested: its quote was verified on NEAR

Zero-knowledge proofno record yet

A zero-knowledge proof of the verdict

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.

Check it yourself

antibody zk status --run 117

How the zero-knowledge proof works (docs/zk.md)