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

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

Run · re-run · program 12

Run 165

A re-run of commit 60'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: bc14e73ef8430738…, receipt sha256: bc14e73ef8430738020c4ac3a7ff07a75a74f0ad0f1e4aea2f84ea4b4c99e257
Request sha256: 10ed0bbdadf94699…, request sha256: 10ed0bbdadf946993b587db16bd056d8018c0c8e6353b266a21e92532e806bab
The SHA-256 of the input near-antibody sent the enclave: its result and its attestation bind to the same bytes.
Output sha256: 3b9709dc0d5e4bb1…, output sha256: 3b9709dc0d5e4bb1c350b682cc5f3a7a9dc8338349a02167d5d794f74f9f2b4e
The SHA-256 of the facts near-antibody received: the TDX quote binds it.
Mode extras: none
Started: 2026-11-09 00:13:31 UTCDBifmR1E…, NEAR transaction: DBifmR1EcaHohDnxEgLQhH29SetR7PafNMKY8vc541dZ, opens an explorer in a new tab
Answered: 2026-11-09 00:13:44 UTC13 s after it was requestedDBifmR1E…, NEAR transaction: DBifmR1EcaHohDnxEgLQhH29SetR7PafNMKY8vc541dZ, opens an explorer in a new tab
Commit: Commit 60
Program: Program 12round 10
Paid for by: keeper.antibody.testnet, account: keeper.antibody.testnet our account

No violationno rule broken

receipt bc14e73ef843…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.001 wNEAR bond, by our fixture agent F (agent-f.antibody.testnet). Nobody, the project included, can read it before its verdict.
9KvRqDuY…, NEAR transaction: 9KvRqDuYBubWDTX9ArbrExifpq5PNKw7xdAsFG6BYYn, opens an explorer in a new tab2026-11-0817:14:42 UTC · block 276,804,942
7.0 h later
+7.0 h after the commit's block
Re-run requested at round 10's fix · run 165
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).
DBifmR1E…, NEAR transaction: DBifmR1EcaHohDnxEgLQhH29SetR7PafNMKY8vc541dZ, 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 bc14e73ef843…, receipt sha256: bc14e73ef8430738020c4ac3a7ff07a75a74f0ad0f1e4aea2f84ea4b4c99e257. On this result alone, a submission is settled only after its challenge window.

Delivered in DBifmR1E…, NEAR transaction: DBifmR1EcaHohDnxEgLQhH29SetR7PafNMKY8vc541dZ, opens an explorer in a new tab

Check it yourself

antibody status --run 165

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

{
  "commit": 60,
  "id": 165,
  "mode": "rerun",
  "outcome": {
    "Answered": {
      "at": 1794183224,
      "facts": {
        "extra": "None",
        "impact_usd_micro": "0",
        "keys": [],
        "kind": "NoViolation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "bc14e73ef8430738020c4ac3a7ff07a75a74f0ad0f1e4aea2f84ea4b4c99e257"
      },
      "output_sha256": "3b9709dc0d5e4bb1c350b682cc5f3a7a9dc8338349a02167d5d794f74f9f2b4e",
      "tier": "T1"
    }
  },
  "payer": "keeper.antibody.testnet",
  "program": 12,
  "request_sha256": "10ed0bbdadf946993b587db16bd056d8018c0c8e6353b266a21e92532e806bab",
  "round": 10,
  "signer": "keeper.antibody.testnet",
  "started_at": 1794183211
}

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

Check it yourself

tx DBifmR1Eca… · NEAR archival RPC

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

outlayer-verify tx DBifmR1EcaHohDnxEgLQhH29SetR7PafNMKY8vc541dZ

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

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 165

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