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

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

Run · re-run · program 0

Run 19

A re-run of commit 5's proof at round 2'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: e3e5e91eb7111ff5…, receipt sha256: e3e5e91eb7111ff5be345d88c741abeeb7410c7d4429147c6f9332b5ef34f0bf
Request sha256: 7e838836e2c3b029…, request sha256: 7e838836e2c3b029d7460ecb97b50482bcd94f09f95621d168b84807d4e0dbf0
The SHA-256 of the input near-antibody sent the enclave: its result and its attestation bind to the same bytes.
Output sha256: 843bb8f52fc2a22a…, output sha256: 843bb8f52fc2a22a8051fb6905e5b61351b06bb9a4f141eaa86a0147323cfa3f
The SHA-256 of the facts near-antibody received: the TDX quote binds it.
Mode extras: none
Started: 2026-11-03 12:11:32 UTC
Answered: 2026-11-03 12:11:46 UTC14 s after it was requested
Commit: Commit 5
Program: Program 0round 2
Paid for by: keeper.antibody.testnet, account: keeper.antibody.testnet our account

No violationno rule broken

receipt e3e5e91eb711…

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 e3e5e91eb711…, receipt sha256: e3e5e91eb7111ff5be345d88c741abeeb7410c7d4429147c6f9332b5ef34f0bf. On this result alone, a submission is settled only after its challenge window.

Check it yourself

antibody status --run 19

Attested on NEAR

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": 19}

{
  "commit": 5,
  "id": 19,
  "mode": "rerun",
  "outcome": {
    "Answered": {
      "at": 1793707906,
      "facts": {
        "extra": "None",
        "impact_usd_micro": "0",
        "keys": [],
        "kind": "NoViolation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "e3e5e91eb7111ff5be345d88c741abeeb7410c7d4429147c6f9332b5ef34f0bf"
      },
      "output_sha256": "843bb8f52fc2a22a8051fb6905e5b61351b06bb9a4f141eaa86a0147323cfa3f",
      "tier": "T1"
    }
  },
  "payer": "keeper.antibody.testnet",
  "program": 0,
  "request_sha256": "7e838836e2c3b029d7460ecb97b50482bcd94f09f95621d168b84807d4e0dbf0",
  "round": 2,
  "signer": "keeper.antibody.testnet",
  "started_at": 1793707892
}

Check it yourself

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

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

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 19

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

What the enclave answered

How it is checked

What the enclave answered

The raw record

Its Intel TDX quote, verified on NEAR

A zero-knowledge proof of the verdict