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

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

Run · re-run · program 12

Run 166

A re-run of commit 61's proof at round 10'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: ffe4160b3cc2f5b4…, receipt sha256: ffe4160b3cc2f5b40c27748d30fc7320d9e1485f0cba581c72cc3c00e7e431a7
Request sha256: 724b9a96b8899b92…, request sha256: 724b9a96b8899b928fc334db7d9ca968e2e8b6155d69d8d8df7e739d75adf46c
The SHA-256 of the input near-antibody sent the enclave: its result and its attestation bind to the same bytes.
Output sha256: 1e9213f1e722e3f6…, output sha256: 1e9213f1e722e3f669ba12e1be6f40cad7732f03476bd3cc5a15baf00ef880dd
The SHA-256 of the facts near-antibody received: the TDX quote binds it.
Mode extras: none
Started: 2026-11-09 00:13:48 UTCFPK1a3nx…, NEAR transaction: FPK1a3nxYAyhCjqPX7HsmavnQt4TyiiUfYssZtDFdXy7, opens an explorer in a new tab
Answered: 2026-11-09 00:14:02 UTC14 s after it was requestedFPK1a3nx…, NEAR transaction: FPK1a3nxYAyhCjqPX7HsmavnQt4TyiiUfYssZtDFdXy7, opens an explorer in a new tab
Commit: Commit 61
Program: Program 12round 10
Paid for by: keeper.antibody.testnet, account: keeper.antibody.testnet our account

No violationno rule broken

receipt ffe4160b3cc2…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.001 wNEAR bond, by our fixture agent G (agent-g.antibody.testnet). Nobody, the project included, can read it before its verdict.
5hMm5fc1…, NEAR transaction: 5hMm5fc1594nMxKiD6Ch9FNa2BqWSBQhXuVxjpiQzvSe, opens an explorer in a new tab2026-11-0817:15:14 UTC · block 276,804,994
7.0 h later
+7.0 h after the commit's block
Re-run requested at round 10's fix · run 166
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).
FPK1a3nx…, NEAR transaction: FPK1a3nxYAyhCjqPX7HsmavnQt4TyiiUfYssZtDFdXy7, 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 ffe4160b3cc2…, receipt sha256: ffe4160b3cc2f5b40c27748d30fc7320d9e1485f0cba581c72cc3c00e7e431a7. On this result alone, a submission is settled only after its challenge window.

Delivered in FPK1a3nx…, NEAR transaction: FPK1a3nxYAyhCjqPX7HsmavnQt4TyiiUfYssZtDFdXy7, opens an explorer in a new tab

Check it yourself

antibody status --run 166

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

{
  "commit": 61,
  "id": 166,
  "mode": "rerun",
  "outcome": {
    "Answered": {
      "at": 1794183242,
      "facts": {
        "extra": "None",
        "impact_usd_micro": "0",
        "keys": [],
        "kind": "NoViolation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "ffe4160b3cc2f5b40c27748d30fc7320d9e1485f0cba581c72cc3c00e7e431a7"
      },
      "output_sha256": "1e9213f1e722e3f669ba12e1be6f40cad7732f03476bd3cc5a15baf00ef880dd",
      "tier": "T1"
    }
  },
  "payer": "keeper.antibody.testnet",
  "program": 12,
  "request_sha256": "724b9a96b8899b928fc334db7d9ca968e2e8b6155d69d8d8df7e739d75adf46c",
  "round": 10,
  "signer": "keeper.antibody.testnet",
  "started_at": 1794183228
}

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 BwQUjxby…, NEAR transaction: BwQUjxbyDvqXePbPLzUVirXZwdJbW9SFrEYv6eUBc7kK, opens an explorer in a new tab

Check it yourself

tx FPK1a3nxYA… · NEAR archival RPC

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

outlayer-verify tx FPK1a3nxYAyhCjqPX7HsmavnQt4TyiiUfYssZtDFdXy7

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

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 166

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