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

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

Run · verification · program 13

Run 150

The enclave's verification of commit 65'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) · lowba3b7b9d03ff…, tag of slot 0: ba3b7b9d03ffc9856d37b1a69139b982862175d907616e3c191c9294998fbeb7

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

676bfef1d68894fc…

Request sha256

1156cdf6d85471e9…

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

Output sha256

d96bc7e8476a36d6…

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 22:15:10 UTC7ERAU5ev…

Answered

2026-11-08 22:15:24 UTC14 s after it was requested7ERAU5ev…

Commit

Commit 65

Program

Program 13round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

e9c6c01dadc.practice.antibody.testnet a visitor's practice try

Violationvault keeps its ether · low

receipt 676bfef1d688…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.0001 wNEAR bond, by a visitor's practice try (e9c6c01dadc.practice.antibody.testnet).
yiT5sypu…, NEAR transaction: yiT5sypu5NXZ6R9P9rbWvMXduULKizF9jfrbHRedX8r, opens an explorer in a new tab2026-11-0822:15:08 UTC · block 276,835,045
+1.8 s after the commit's block
Revealed · run 150 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 1156cdf6d854…, request sha256: 1156cdf6d85471e9380e6d8156794de2534cff2adeca08747154cb55f115df4d). 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 676bfef1d688…, receipt sha256: 676bfef1d68894fc238ffabdb3b09f99eab3b79643e0bd130911613b26b9d360. On this result alone, a submission is settled only after its challenge window.

Delivered in 7ERAU5ev…, NEAR transaction: 7ERAU5ev3Hc99RaEJ1tjHcvDCrqhPCkxfjdktFi7G35z, opens an explorer in a new tab

Check it yourself

antibody status --run 150

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

{
  "commit": 65,
  "id": 150,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794176124,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "dc4cfab42401a78ab968fcc56b747cc742ee25bb39187f93434af6ef90f910270e90de34cf233a503211c44c958a93e9aa1c223361d42bd44e6c8e2f"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "ba3b7b9d03ffc9856d37b1a69139b982862175d907616e3c191c9294998fbeb7"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "676bfef1d68894fc238ffabdb3b09f99eab3b79643e0bd130911613b26b9d360"
      },
      "output_sha256": "d96bc7e8476a36d6f4f2759a363243794fd442dc2b256b0e8a76acc96f4795c3",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 13,
  "request_sha256": "1156cdf6d85471e9380e6d8156794de2534cff2adeca08747154cb55f115df4d",
  "round": 0,
  "signer": "e9c6c01dadc.practice.antibody.testnet",
  "started_at": 1794176110
}

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

Check it yourself

tx 7ERAU5ev3H… · NEAR archival RPC

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

outlayer-verify tx 7ERAU5ev3Hc99RaEJ1tjHcvDCrqhPCkxfjdktFi7G35z

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

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

Check it yourself

What its public values bind

Request sha256: 1156cdf6d854…, the proof's request sha256: 1156cdf6d85471e9380e6d8156794de2534cff2adeca08747154cb55f115df4d; equals the run's
Run · round · commit: 150 · 0 · 65; equals near-antibody's
Blob sha256: 8a30c01e52e0…, blob sha256: 8a30c01e52e0f96f7d43e63ea75e2d437002680abc4ddd62a5c842db76dc3517; 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: 676bfef1d688…, the proof's receipt sha256: 676bfef1d68894fc238ffabdb3b09f99eab3b79643e0bd130911613b26b9d360; 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 150

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

Holds if: near-t2's record says confirmed

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