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

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

Run · verification · program 13

Run 143

The enclave's verification of commit 63'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) · low1c4489f727ea…, tag of slot 0: 1c4489f727ea0e851d7c5f3ff1c4054966e5649ae4da6dde6315a8ccc588ad9f

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

ce0c0ae9403322db…

Request sha256

276ba1bf2cd386dd…

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

Output sha256

30fcaf469a41bd22…

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:04:52 UTCAxnmm1WD…

Answered

2026-11-08 21:05:05 UTC13 s after it was requestedAxnmm1WD…

Commit

Commit 63

Program

Program 13round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

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

Violationvault keeps its ether · low

receipt ce0c0ae94033…

Timeline

Every step is a NEAR transaction, timed by block from commit 63'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-1-p13.practice.antibody.testnet).
5KXy3set…, NEAR transaction: 5KXy3setDhJFGzXkU6YLX739567KTDezEKwSvZAYxfoa, opens an explorer in a new tab2026-11-0821:04:50 UTC · block 276,828,101
+2.4 s after the commit's block
Revealed · run 143 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 276ba1bf2cd3…, request sha256: 276ba1bf2cd386dd91fd39030a9049a87e7defe5464eab1a084de7dd7b6f04c6). 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 ce0c0ae94033…, receipt sha256: ce0c0ae9403322dbf0af75ee446d50d9db262e68fae7a4cae69b7f824589c28b. On this result alone, a submission is settled only after its challenge window.

Delivered in Axnmm1WD…, NEAR transaction: Axnmm1WDU7qQ43axV2uWiDwpj7q7Vim9PMknjj4yV1sZ, opens an explorer in a new tab

Check it yourself

antibody status --run 143

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

{
  "commit": 63,
  "id": 143,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794171905,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "f52f450ea7e22bbdce0e8e42e7f412474de357b1ce173abf28b6b27039e3e5fb95296f832cd4684893de76f544f55438b588a46489309529a8095571"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "1c4489f727ea0e851d7c5f3ff1c4054966e5649ae4da6dde6315a8ccc588ad9f"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "ce0c0ae9403322dbf0af75ee446d50d9db262e68fae7a4cae69b7f824589c28b"
      },
      "output_sha256": "30fcaf469a41bd222f433bd20e8604278901da5ced1f2bd076576d38c122073e",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 13,
  "request_sha256": "276ba1bf2cd386dd91fd39030a9049a87e7defe5464eab1a084de7dd7b6f04c6",
  "round": 0,
  "signer": "judge-1-p13.practice.antibody.testnet",
  "started_at": 1794171892
}

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

Check it yourself

tx Axnmm1WDU7… · NEAR archival RPC

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

outlayer-verify tx Axnmm1WDU7qQ43axV2uWiDwpj7q7Vim9PMknjj4yV1sZ

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

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

Check it yourself

What its public values bind

Request sha256: 276ba1bf2cd3…, the proof's request sha256: 276ba1bf2cd386dd91fd39030a9049a87e7defe5464eab1a084de7dd7b6f04c6; equals the run's
Run · round · commit: 143 · 0 · 63; equals near-antibody's
Blob sha256: 4a0beaa837a3…, blob sha256: 4a0beaa837a3cf347dbabefb312bb533468c8bb3e47c7e770f1ee0d605a99425; 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: ce0c0ae94033…, the proof's receipt sha256: ce0c0ae9403322dbf0af75ee446d50d9db262e68fae7a4cae69b7f824589c28b; 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 143

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

Holds if: near-t2's record says confirmed

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