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

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

Run · re-run · program 5

Run 42

A re-run of commit 13's proof at round 1'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: 3fd2220ad3759c55…, receipt sha256: 3fd2220ad3759c5529031c209bac0ff80d086016a19844aed21ef984e49aed7b
Request sha256: f67d4f308df203d3…, request sha256: f67d4f308df203d3dffa842d7c9601d7623dfc15f9d812946184e12ff31cacb6
The SHA-256 of the input near-antibody sent the enclave: its result and its attestation bind to the same bytes.
Output sha256: ea6149ca05c7f734…, output sha256: ea6149ca05c7f734294fb1d2cec5b9717a90e1a6fe9fc732ec06b8dda493ac91
The SHA-256 of the facts near-antibody received: the TDX quote binds it.
Mode extras: none
Started: 2026-11-04 15:55:46 UTC65Pb7sAQ…, NEAR transaction: 65Pb7sAQKjgvgd3CYM9KaK5VsMKpmtMBwZ8hXbzLdBz3, opens an explorer in a new tab
Answered: 2026-11-04 15:55:59 UTC13 s after it was requested65Pb7sAQ…, NEAR transaction: 65Pb7sAQKjgvgd3CYM9KaK5VsMKpmtMBwZ8hXbzLdBz3, opens an explorer in a new tab
Commit: Commit 13
Program: Program 5round 1
Paid for by: keeper.antibody.testnet, account: keeper.antibody.testnet our account

No violationno rule broken

receipt 3fd2220ad375…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.001 wNEAR bond, by our fixture agent A (agent-a.antibody.testnet). Nobody, the project included, can read it before its verdict.
CynCsx8P…, NEAR transaction: CynCsx8PNsFAYnYp6Zk5HjpSg3fWUrHSKfJ9CD9HQ3nP, opens an explorer in a new tab2026-11-0415:42:11 UTC · block 276,214,742
+13.6 min after the commit's block
Re-run requested at round 1's fix · run 42
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).
65Pb7sAQ…, NEAR transaction: 65Pb7sAQKjgvgd3CYM9KaK5VsMKpmtMBwZ8hXbzLdBz3, 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 3fd2220ad375…, receipt sha256: 3fd2220ad3759c5529031c209bac0ff80d086016a19844aed21ef984e49aed7b. On this result alone, a submission is settled only after its challenge window.

Delivered in 65Pb7sAQ…, NEAR transaction: 65Pb7sAQKjgvgd3CYM9KaK5VsMKpmtMBwZ8hXbzLdBz3, opens an explorer in a new tab

Check it yourself

antibody status --run 42

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

{
  "commit": 13,
  "id": 42,
  "mode": "rerun",
  "outcome": {
    "Answered": {
      "at": 1793807759,
      "facts": {
        "extra": "None",
        "impact_usd_micro": "0",
        "keys": [],
        "kind": "NoViolation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "3fd2220ad3759c5529031c209bac0ff80d086016a19844aed21ef984e49aed7b"
      },
      "output_sha256": "ea6149ca05c7f734294fb1d2cec5b9717a90e1a6fe9fc732ec06b8dda493ac91",
      "tier": "T1"
    }
  },
  "payer": "keeper.antibody.testnet",
  "program": 5,
  "request_sha256": "f67d4f308df203d3dffa842d7c9601d7623dfc15f9d812946184e12ff31cacb6",
  "round": 1,
  "signer": "keeper.antibody.testnet",
  "started_at": 1793807746
}

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

Check it yourself

tx 65Pb7sAQKj… · NEAR archival RPC

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

outlayer-verify tx 65Pb7sAQKjgvgd3CYM9KaK5VsMKpmtMBwZ8hXbzLdBz3

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

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 42

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