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

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

Run · verification · program 10

Run 141

The enclave's verification of commit 62'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) · lowd6dc341d7e4a…, tag of slot 0: d6dc341d7e4a15f3f2cb66266a12099c27838232d7c678e84b6dde21eb84602a

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

8bf64b138bd7839d…

Request sha256

cbbfb5e0c42e74b4…

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

Output sha256

8224505dcf3e326e…

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:00:16 UTC7muEEJVj…

Answered

2026-11-08 21:00:30 UTC14 s after it was requested7muEEJVj…

Commit

Commit 62

Program

Program 10round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

pcs-check.practice.antibody.testnet our rehearsal

Violationvault keeps its ether · low

receipt 8bf64b138bd7…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.0001 wNEAR bond, by our rehearsal (pcs-check.practice.antibody.testnet).
2WeeiR8y…, NEAR transaction: 2WeeiR8yV3Gvx4cyApduiZ5yvoHt5xLj9qUY6PkhF9tK, opens an explorer in a new tab2026-11-0821:00:14 UTC · block 276,827,645
+1.9 s after the commit's block
Revealed · run 141 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 cbbfb5e0c42e…, request sha256: cbbfb5e0c42e74b4cf453af5173a310a6d9eac956ed0160a5e99bf098d266b1e). 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 8bf64b138bd7…, receipt sha256: 8bf64b138bd7839d74909e98977fa5b199f08150c53c4fd5c0acbc43325c09b5. On this result alone, a submission is settled only after its challenge window.

Delivered in 7muEEJVj…, NEAR transaction: 7muEEJVjH4S5TCfVPNZgFsUxufFB56DC7yoXjZZne1Ff, opens an explorer in a new tab

Check it yourself

antibody status --run 141

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

{
  "commit": 62,
  "id": 141,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794171630,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "709c5d08e3558828c748872a3a15ccd24f8341f3cd0b0acad64070af5a9389ec4f43936c1398590963998d4abb7d2c3a0a3b40d63d861408cfe1479a"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "d6dc341d7e4a15f3f2cb66266a12099c27838232d7c678e84b6dde21eb84602a"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "8bf64b138bd7839d74909e98977fa5b199f08150c53c4fd5c0acbc43325c09b5"
      },
      "output_sha256": "8224505dcf3e326e6111f8ec237bd213003c11c2c1311ce21c838baa9704ecc2",
      "tier": "T0"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 10,
  "request_sha256": "cbbfb5e0c42e74b4cf453af5173a310a6d9eac956ed0160a5e99bf098d266b1e",
  "round": 0,
  "signer": "pcs-check.practice.antibody.testnet",
  "started_at": 1794171616
}

Attested on NEARnot yet

Its Intel TDX quote, verified on NEAR

Not attested on NEAR: the verdict stands on the enclave's result and its challenge window. Our attestation relayer sends each answered run's quote, and anyone may.

Check it yourself

tx 7muEEJVjH4… · NEAR archival RPC

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

outlayer-verify tx 7muEEJVjH4S5TCfVPNZgFsUxufFB56DC7yoXjZZne1Ff

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

Holds if: the run's answer is the enclave's result, not attested

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

Check it yourself

What its public values bind

Request sha256: cbbfb5e0c42e…, the proof's request sha256: cbbfb5e0c42e74b4cf453af5173a310a6d9eac956ed0160a5e99bf098d266b1e; equals the run's
Run · round · commit: 141 · 0 · 62; equals near-antibody's
Blob sha256: bd73e5bffccf…, blob sha256: bd73e5bffccf3f5e87a9d8a9357029af924d71170ba600275f8bd57129a8c336; bound
Base sha256: fabfae18046d…, base witness sha256: fabfae18046d84a980776a07b58a1ce5deb47f68fc5117af45b63071de0c3be9; bound
Manifest sha256: 526e4d527444…, manifest sha256: 526e4d5274449d7048ea608f02169488549ca7e8f5e8b3c7bbd684f5ea292756; bound
Anchor: block 12089348 on Sepolia; bound
Program key · verifier: bounty.antibody.testnet/10 · 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: 8bf64b138bd7…, the proof's receipt sha256: 8bf64b138bd7839d74909e98977fa5b199f08150c53c4fd5c0acbc43325c09b5; 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 141

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

Holds if: near-t2's record says confirmed

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