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

Run 144 · verification · Violation · Zero-knowledge proof · Antibody

Run · verification · program 13

Run 144

The enclave's verification of commit 64's sealed proof: Violation of the “vault keeps its ether” rule.

ViolationZero-knowledge proof

What the enclave answered

The run as near-antibody records it: every hash below is checkable against NEAR.

Mode

verify

Verification: the enclave judged a sealed submission.

Kind

Violation

Keys

slot 0 (vault_keeps_its_ether) · lowabbae26af73f…, tag of slot 0: abbae26af73f217688e8ade9bde510baded8467efc6bcda8d5f5ce3874a5a5b7

Impact

$0.00 fixture USD

min(protocol loss, attacker gain), at the manifest's committed prices, in the fixture's own dollars.

Protected harm

$0.00 fixture USD

Loss on the accounts the program declared protected: above its threshold, a proof that breaks no rule is a gap claim.

Level

Zero-knowledge proofZK proof confirmed

Receipt sha256

e8bb19bc57b1343b…

Request sha256

3ceead94cd4abe9d…

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

Output sha256

2ddc35ef00422869…

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

Mode extras

a disclosure wrap (wrap_d): if its tag and round are disclosed, their key opens the proof

Started

2026-11-08 21:05:34 UTCGaKqTQPy…

Answered

2026-11-08 21:05:48 UTC14 s after it was requestedGaKqTQPy…

Commit

Commit 64

Program

Program 13round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

judge-2-p13.practice.antibody.testnet our check of a fresh practice program

Violationvault keeps its ether · low

receipt e8bb19bc57b1…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.0001 wNEAR bond, by our check of a fresh practice program (judge-2-p13.practice.antibody.testnet).
BX1pdB5y…, NEAR transaction: BX1pdB5ycM5pTKrfR3xAsQ4EENBQ3Zkqk9dB1GShtco5, opens an explorer in a new tab2026-11-0821:05:31 UTC · block 276,828,170
+2.5 s after the commit's block
Revealed · run 144 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 3ceead94cd4a…, request sha256: 3ceead94cd4abe9de2e25a5ba2151d302f67e39493104c2a06e04991c2d0555c). The run was paid for by the practice vending contract (practice.antibody.testnet).

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 e8bb19bc57b1…, receipt sha256: e8bb19bc57b1343b4cbcf5845aae35b91a7d4db41571102398ba44fedca4eecd. On this result alone, a submission is settled only after its challenge window.

Delivered in GaKqTQPy…, NEAR transaction: GaKqTQPyHcAqGx4FSDnpk4eifaY12zwT9KfGEBZ4Zd9Z, opens an explorer in a new tab

Check it yourself

antibody status --run 144

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

{
  "commit": 64,
  "id": 144,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794171948,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "0f0756cfe2cfb71e47298faa4960a29d58b0a561c08bd5ecd3c63b17707101b00e901edca6fec26eb9039f4ed48204664dd8998f13a28e5bb71a87af"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "abbae26af73f217688e8ade9bde510baded8467efc6bcda8d5f5ce3874a5a5b7"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "e8bb19bc57b1343b4cbcf5845aae35b91a7d4db41571102398ba44fedca4eecd"
      },
      "output_sha256": "2ddc35ef00422869c5882abb40acf570f1937cdc5b68de1ec1f97584938cef46",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 13,
  "request_sha256": "3ceead94cd4abe9de2e25a5ba2151d302f67e39493104c2a06e04991c2d0555c",
  "round": 0,
  "signer": "judge-2-p13.practice.antibody.testnet",
  "started_at": 1794171934
}

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. Instant payouts need it.

Attested in BxeVkxL2…, NEAR transaction: BxeVkxL24HxZnCEsbGAdhmFUxj5cQcfb3xUefvayVRzD, opens an explorer in a new tab

Check it yourself

tx GaKqTQPyHc… · NEAR archival RPC

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

outlayer-verify tx GaKqTQPyHcAqGx4FSDnpk4eifaY12zwT9KfGEBZ4Zd9Z

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

Holds if: the run is attested: its quote was verified on NEAR

Zero-knowledge proofconfirmed on NEAR

A zero-knowledge proof of the verdict

near-t2 verified an SP1 proof that the verifier, re-run on the enclave's exact input, gives the enclave's receipt, kind and rules, and compared every bound value with near-antibody's records. It claims no privacy (anyone can open the proof it re-runs: disclosed, or under a published or public content key), and no payout depends on it.

Recorded on NEAR in 8CByhcRv…, NEAR transaction: 8CByhcRvaYqTfQXPUFyHgeDuHnU8GJXjLFh95eEBUVSd, opens an explorer in a new tab

Check it yourself

What its public values bind

Request sha256: 3ceead94cd4a…, the proof's request sha256: 3ceead94cd4abe9de2e25a5ba2151d302f67e39493104c2a06e04991c2d0555c; equals the run's
Run · round · commit: 144 · 0 · 64; equals near-antibody's
Blob sha256: 7c415fb4d2f4…, blob sha256: 7c415fb4d2f4b578771989582686979bb7eaf8f2f3d13b83a767dee4ed52dc7d; bound
Base sha256: 278f2e646433…, base witness sha256: 278f2e64643326d667657c14aab5d9a1c37d453a559052a123f55161c32fd14e; bound
Manifest sha256: 83e8be420794…, manifest sha256: 83e8be42079439ecbf8d631eba198e86cbd3a2f9e32ea79413d9c8841b0be68c; bound
Anchor: block 12092947 on Sepolia; bound
Program key · verifier: bounty.antibody.testnet/13 · antibody-verifier 0.1.0 revm 38.0.0 reth v2.2.0 rsp 5afe72eb12a2d6accd9d7fdff66785d91cbc8e72 ccc27f0ca6…, the verifier wasm sha256 near-t2 pins: ccc27f0ca60c503c46f6f1b2024b54481709fdd0c8849fe8d9a8912c637b28c1; bound
Receipt sha256: e8bb19bc57b1…, the proof's receipt sha256: e8bb19bc57b1343b4cbcf5845aae35b91a7d4db41571102398ba44fedca4eecd; equals the enclave's
Kind: Violation; equals the enclave's
Slots (severity): 0 low; equals the enclave's

A different request, run, blob, base, manifest, anchor, program, verifier or severity is rejected outright; a different receipt, kind or slots is recorded as a contradiction.

antibody zk status --run 144

view zk.antibody.testnet.get_record({"run_id":"144"})

Holds if: near-t2's record says confirmed

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