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

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

Run · re-run · program 5

Run 46

A re-run of commit 19'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)30c0b9722351…, tag of slot 3: 30c0b97223514767f0cc2a354d396d9d48b7543a097552c44f841ed19af4d301

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

097b488d9d83efe4…

Request sha256

25f7a36e354d6cd6…

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

Output sha256

2e862bb104bc7975…

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

Mode extras

none

Started

2026-11-04 15:57:54 UTC46vT7EYs…

Answered

2026-11-04 15:58:08 UTC14 s after it was requested46vT7EYs…

Commit

Commit 19

Program

Program 5round 1

Paid for by

keeper.antibody.testnet our account

Violationprotected balances · medium

receipt 097b488d9d83…

Timeline

Every step is a NEAR transaction, timed by block from commit 19'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.
8S2QVg9s…, NEAR transaction: 8S2QVg9snxcewMhewuUUHncVj7pexQRsQ6Deh63MUTpu, opens an explorer in a new tab2026-11-0415:49:31 UTC · block 276,215,510
+8.4 min after the commit's block
Re-run requested at round 1's fix · run 46
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).
46vT7EYs…, NEAR transaction: 46vT7EYsyhbo8MdoYPRuqZkKPVSBGuKBH3JcEr13LjS2, 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 097b488d9d83…, receipt sha256: 097b488d9d83efe488292fb4fd08830072e3df6119ca7a6dc728c176e3c20920. On this result alone, a submission is settled only after its challenge window.

Delivered in 46vT7EYs…, NEAR transaction: 46vT7EYsyhbo8MdoYPRuqZkKPVSBGuKBH3JcEr13LjS2, opens an explorer in a new tab

Check it yourself

antibody status --run 46

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

{
  "commit": 19,
  "id": 46,
  "mode": "rerun",
  "outcome": {
    "Answered": {
      "at": 1793807888,
      "facts": {
        "extra": "None",
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 3,
            "tag": "30c0b97223514767f0cc2a354d396d9d48b7543a097552c44f841ed19af4d301"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "097b488d9d83efe488292fb4fd08830072e3df6119ca7a6dc728c176e3c20920"
      },
      "output_sha256": "2e862bb104bc79755949d52153811c7378d9714eb6cb758d5be8bbbd0d0a9e8a",
      "tier": "T1"
    }
  },
  "payer": "keeper.antibody.testnet",
  "program": 5,
  "request_sha256": "25f7a36e354d6cd613b7e8ad6e15ea5a22aaaf22be4be6f6bcd47b3d679c106c",
  "round": 1,
  "signer": "keeper.antibody.testnet",
  "started_at": 1793807874
}

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

Check it yourself

tx 46vT7EYsyh… · NEAR archival RPC

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

outlayer-verify tx 46vT7EYsyhbo8MdoYPRuqZkKPVSBGuKBH3JcEr13LjS2

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

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 46

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