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

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

Run · re-run · program 12

Run 109

A re-run of commit 61's proof at round 1's code and rules: it still breaks the “protected balances” 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 3 (protected_balances) · medium (added by a round)5ab05318e898…, tag of slot 3: 5ab05318e898a8a7683490044fe6d51fb3aff4547a3fe55157766d05e0b40815

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

acf883a5bba1119d…

Request sha256

b93fcbfa21882821…

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

Output sha256

4c93c8c2a03fc36d…

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

Mode extras

none

Started

2026-11-08 17:20:46 UTCAnM7f3t9…

Answered

2026-11-08 17:20:59 UTC13 s after it was requestedAnM7f3t9…

Commit

Commit 61

Program

Program 12round 1

Paid for by

keeper.antibody.testnet our account

Violationprotected balances · medium

receipt acf883a5bba1…

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
+5.5 min after the commit's block
Re-run requested at round 1's fix · run 109
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).
AnM7f3t9…, NEAR transaction: AnM7f3t9WWACzseRXmK4mPzJiiUn4ZYLegPL3SF79fHs, 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 acf883a5bba1…, receipt sha256: acf883a5bba1119de14623e6756289d27d05c2d70bccd531fd6f38bcda9ee1cf. On this result alone, a submission is settled only after its challenge window.

Delivered in AnM7f3t9…, NEAR transaction: AnM7f3t9WWACzseRXmK4mPzJiiUn4ZYLegPL3SF79fHs, opens an explorer in a new tab

Check it yourself

antibody status --run 109

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

{
  "commit": 61,
  "id": 109,
  "mode": "rerun",
  "outcome": {
    "Answered": {
      "at": 1794158459,
      "facts": {
        "extra": "None",
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 3,
            "tag": "5ab05318e898a8a7683490044fe6d51fb3aff4547a3fe55157766d05e0b40815"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "acf883a5bba1119de14623e6756289d27d05c2d70bccd531fd6f38bcda9ee1cf"
      },
      "output_sha256": "4c93c8c2a03fc36d11feba658e99445d518df349b4844a8b21aba9d29ad6853b",
      "tier": "T1"
    }
  },
  "payer": "keeper.antibody.testnet",
  "program": 12,
  "request_sha256": "b93fcbfa21882821621eee6e7e7995bb8afec291336380772ab6a2f03858b256",
  "round": 1,
  "signer": "keeper.antibody.testnet",
  "started_at": 1794158446
}

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

Check it yourself

tx AnM7f3t9WW… · NEAR archival RPC

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

outlayer-verify tx AnM7f3t9WWACzseRXmK4mPzJiiUn4ZYLegPL3SF79fHs

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

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 109

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