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

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

Run · verification · program 13

Run 161

The enclave's verification of commit 71'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) · lowef4d2b7b7a15…, tag of slot 0: ef4d2b7b7a153bf30ed4a02f46be81385eab5ce7de343b80e083310186f1dd63

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

4289a52656afe36e…

Request sha256

beb18690be1756bc…

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

Output sha256

961f4f39885cc0ec…

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 23:34:03 UTC3RuHSJHo…

Answered

2026-11-08 23:34:21 UTC18 s after it was requested3RuHSJHo…

Commit

Commit 71

Program

Program 13round 0

Paid for by

antibody.testnet the program's project

Signed by

capdemo.antibody.testnet our account

Violationvault keeps its ether · low

receipt 4289a52656af…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.0001 wNEAR bond, by our account (capdemo.antibody.testnet).
DHGQ3oaX…, NEAR transaction: DHGQ3oaXsdRVcRHtwFyxvLL33mTGmVEWmPohh88BdDFQ, opens an explorer in a new tab2026-11-0823:33:13 UTC · block 276,842,790
+49.9 s after the commit's block
Revealed · run 161 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 beb18690be17…, request sha256: beb18690be1756bc649dcee124b8ccbc9317e283354326b82b143c38db181c19). The run was paid for by the project (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 4289a52656af…, receipt sha256: 4289a52656afe36e3ddb8c01c776f00325274db40a0e15f6036b9a940913390b. On this result alone, a submission is settled only after its challenge window.

Delivered in 3RuHSJHo…, NEAR transaction: 3RuHSJHoXSiRGvXBCfWAk7ZbNoVQ9PKYrCCsHtxyJJbN, opens an explorer in a new tab

Check it yourself

antibody status --run 161

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

{
  "commit": 71,
  "id": 161,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794180861,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "a2584bbac8ed3f725adbfc79f4af9a95d1aea4de1790e90905c5885bb496e086056ee79027d22443aee56901d49f560eaa44cf8aa116d77b2fbd0654"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "ef4d2b7b7a153bf30ed4a02f46be81385eab5ce7de343b80e083310186f1dd63"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "4289a52656afe36e3ddb8c01c776f00325274db40a0e15f6036b9a940913390b"
      },
      "output_sha256": "961f4f39885cc0ec9fe7b745079d0c9d912dbf8de28e94a531c4289bcce414c2",
      "tier": "T1"
    }
  },
  "payer": "antibody.testnet",
  "program": 13,
  "request_sha256": "beb18690be1756bc649dcee124b8ccbc9317e283354326b82b143c38db181c19",
  "round": 0,
  "signer": "capdemo.antibody.testnet",
  "started_at": 1794180843
}

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

Check it yourself

tx 3RuHSJHoXS… · NEAR archival RPC

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

outlayer-verify tx 3RuHSJHoXSiRGvXBCfWAk7ZbNoVQ9PKYrCCsHtxyJJbN

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

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

Check it yourself

What its public values bind

Request sha256: beb18690be17…, the proof's request sha256: beb18690be1756bc649dcee124b8ccbc9317e283354326b82b143c38db181c19; equals the run's
Run · round · commit: 161 · 0 · 71; equals near-antibody's
Blob sha256: bbc7f3f11332…, blob sha256: bbc7f3f11332762e746bf773403661bf948665beb0b38610e6e62238ff225672; 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: 4289a52656af…, the proof's receipt sha256: 4289a52656afe36e3ddb8c01c776f00325274db40a0e15f6036b9a940913390b; 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 161

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

Holds if: near-t2's record says confirmed

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