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

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

Run · verification · program 13

Run 158

The enclave's verification of commit 68'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) · lowdab41779bf12…, tag of slot 0: dab41779bf12ccf4ab34fca75f7bbc767dd2bdb006094963b926cc6cfbe8d92f

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

7cacf427b59df34a…

Request sha256

21f766b96dbafd36…

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

Output sha256

488b41404ae5fbee…

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:59:19 UTC7v14CSp6…

Answered

2026-11-08 22:59:33 UTC14 s after it was requested7v14CSp6…

Commit

Commit 68

Program

Program 13round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

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

Violationvault keeps its ether · low

receipt 7cacf427b59d…

Timeline

Every step is a NEAR transaction, timed by block from commit 68'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 (j8wmtr.practice.antibody.testnet).
AuHh9fDV…, NEAR transaction: AuHh9fDVJSb67sF6nPTYoVJyGKQX6gF5Lu6h4zzsqT64, opens an explorer in a new tab2026-11-0822:59:17 UTC · block 276,839,442
+2.4 s after the commit's block
Revealed · run 158 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 21f766b96dba…, request sha256: 21f766b96dbafd36c0e99f70cb52b20a5dc09b64b11be5e562dfaca472bf5092). 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 7cacf427b59d…, receipt sha256: 7cacf427b59df34abc621952badcdf46c98bb2e7b876542c7c5f9daed769dc4b. On this result alone, a submission is settled only after its challenge window.

Delivered in 7v14CSp6…, NEAR transaction: 7v14CSp68fj8oeHdseQz3ABrGCacK4fXzkLhr2BAaSoT, opens an explorer in a new tab

Check it yourself

antibody status --run 158

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

{
  "commit": 68,
  "id": 158,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794178773,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "158ab78e5a2007212203030b2d7b71434ad47cf79f733aab322c5a1402297b4eaf88f3967e1416bc11129f30206c7ca30d54d940d80b7125369935b2"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "dab41779bf12ccf4ab34fca75f7bbc767dd2bdb006094963b926cc6cfbe8d92f"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "7cacf427b59df34abc621952badcdf46c98bb2e7b876542c7c5f9daed769dc4b"
      },
      "output_sha256": "488b41404ae5fbee8b2c03a6d1848b88349b146d48803de5db911f104620dde9",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 13,
  "request_sha256": "21f766b96dbafd36c0e99f70cb52b20a5dc09b64b11be5e562dfaca472bf5092",
  "round": 0,
  "signer": "j8wmtr.practice.antibody.testnet",
  "started_at": 1794178759
}

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

Check it yourself

tx 7v14CSp68f… · NEAR archival RPC

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

outlayer-verify tx 7v14CSp68fj8oeHdseQz3ABrGCacK4fXzkLhr2BAaSoT

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

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

Check it yourself

What its public values bind

Request sha256: 21f766b96dba…, the proof's request sha256: 21f766b96dbafd36c0e99f70cb52b20a5dc09b64b11be5e562dfaca472bf5092; equals the run's
Run · round · commit: 158 · 0 · 68; equals near-antibody's
Blob sha256: f95e02521428…, blob sha256: f95e02521428a19df9335d2ac3191f82544d72150b247005348a622a0d4fad68; 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: 7cacf427b59d…, the proof's receipt sha256: 7cacf427b59df34abc621952badcdf46c98bb2e7b876542c7c5f9daed769dc4b; 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 158

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

Holds if: near-t2's record says confirmed

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