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

Run 108 · re-run · Violation · Attested on NEAR · Antibody

Run · re-run · program 12

Run 108

A re-run of commit 60's proof at round 1's code and rules: it still breaks the solvency rule.

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

Violation

Keys

slot 0 (solvency) · criticalaa08b93ae815…, tag of slot 0: aa08b93ae815a96d0ed7d13d6e8511bf249999f9c512a1fc9d3f0728a5765df6

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

68981bdf9074a894…

Request sha256

6b354599347c9a9f…

The SHA-256 of the input near-antibody sent the enclave: its result and its attestation bind to the same bytes.

Output sha256

558babc514f1f5ad…

The SHA-256 of the facts near-antibody received: the TDX quote binds it.

Mode extras

none

Started

2026-11-08 17:20:31 UTCAnJTuw13…

Answered

2026-11-08 17:20:44 UTC13 s after it was requestedAnJTuw13…

Commit

Commit 60

Program

Program 12round 1

Paid for by

keeper.antibody.testnet our account

Violationsolvency · critical

receipt 68981bdf9074…

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
+5.8 min after the commit's block
Re-run requested at round 1's fix · run 108
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).
AnJTuw13…, NEAR transaction: AnJTuw13RAbj3e8XhXjeCbEZdJH9B7sWa1BF8GSyXV76, 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: Violation, receipt 68981bdf9074…, receipt sha256: 68981bdf9074a894f5a9772a35da8d4aaf6bebcd816991f945ea95ae892edd23. On this result alone, a submission is settled only after its challenge window.

Delivered in AnJTuw13…, NEAR transaction: AnJTuw13RAbj3e8XhXjeCbEZdJH9B7sWa1BF8GSyXV76, opens an explorer in a new tab

Check it yourself

antibody status --run 108

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

{
  "commit": 60,
  "id": 108,
  "mode": "rerun",
  "outcome": {
    "Answered": {
      "at": 1794158444,
      "facts": {
        "extra": "None",
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "aa08b93ae815a96d0ed7d13d6e8511bf249999f9c512a1fc9d3f0728a5765df6"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "68981bdf9074a894f5a9772a35da8d4aaf6bebcd816991f945ea95ae892edd23"
      },
      "output_sha256": "558babc514f1f5ad65e438037d9de98b79a27e55eeda4e95c1198289c765bc08",
      "tier": "T1"
    }
  },
  "payer": "keeper.antibody.testnet",
  "program": 12,
  "request_sha256": "6b354599347c9a9f17f7829adc32b9ccd0b12afbc04bcff8556e2e014382876d",
  "round": 1,
  "signer": "keeper.antibody.testnet",
  "started_at": 1794158431
}

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

Check it yourself

tx AnJTuw13RA… · NEAR archival RPC

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

outlayer-verify tx AnJTuw13RAbj3e8XhXjeCbEZdJH9B7sWa1BF8GSyXV76

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

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 108

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