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

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

Run · verification · program 13

Run 157

The enclave's verification of commit 67'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) · lowf669b028d577…, tag of slot 0: f669b028d5773d33f0c64679a83f82c6759eb5af5feed36be40614616b98dc58

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

d66700f918b45590…

Request sha256

b917ebc2950d1c0a…

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

Output sha256

737037fb3c3ce4ed…

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:26:45 UTCEqcfdWKM…

Answered

2026-11-08 22:27:00 UTC15 s after it was requestedEqcfdWKM…

Commit

Commit 67

Program

Program 13round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

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

Violationvault keeps its ether · low

receipt d66700f918b4…

Timeline

Every step is a NEAR transaction, timed by block from commit 67'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 (j3qzvk.practice.antibody.testnet).
GYXxJ6LK…, NEAR transaction: GYXxJ6LKqmPvCSe8uUa4u7mSTht24VHQEeqLn6vbrqTF, opens an explorer in a new tab2026-11-0822:26:33 UTC · block 276,836,174
+12.1 s after the commit's block
Revealed · run 157 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 b917ebc2950d…, request sha256: b917ebc2950d1c0a1288c598b4dc6743cc821a2dd14c1ea61914370b6929480f). 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 d66700f918b4…, receipt sha256: d66700f918b45590984f3b0c72ddde1fdd4f09615a8974ee317147b0bd96ca0c. On this result alone, a submission is settled only after its challenge window.

Delivered in EqcfdWKM…, NEAR transaction: EqcfdWKMpLE1pWgoN7ub2Gt6XokbjTaF9jdJqnQrjJJk, opens an explorer in a new tab

Check it yourself

antibody status --run 157

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

{
  "commit": 67,
  "id": 157,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794176820,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "49b23eba50ba316bc0d1b550f3c7b7f109812b06ec6361d643333e7e65932d535f0ab6150798033ff56d4b1865e3f27938015549ec2d0f3b1a199ad5"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "f669b028d5773d33f0c64679a83f82c6759eb5af5feed36be40614616b98dc58"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "d66700f918b45590984f3b0c72ddde1fdd4f09615a8974ee317147b0bd96ca0c"
      },
      "output_sha256": "737037fb3c3ce4edb5a75619a2eb937b0749ec7b122a6386fb37afcb782f0642",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 13,
  "request_sha256": "b917ebc2950d1c0a1288c598b4dc6743cc821a2dd14c1ea61914370b6929480f",
  "round": 0,
  "signer": "j3qzvk.practice.antibody.testnet",
  "started_at": 1794176805
}

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

Check it yourself

tx EqcfdWKMpL… · NEAR archival RPC

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

outlayer-verify tx EqcfdWKMpLE1pWgoN7ub2Gt6XokbjTaF9jdJqnQrjJJk

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

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

Check it yourself

What its public values bind

Request sha256: b917ebc2950d…, the proof's request sha256: b917ebc2950d1c0a1288c598b4dc6743cc821a2dd14c1ea61914370b6929480f; equals the run's
Run · round · commit: 157 · 0 · 67; equals near-antibody's
Blob sha256: 3edd0f7aaf9c…, blob sha256: 3edd0f7aaf9c9cfdee88e66215051d4ee872c993f8e19f65a6e09816d023b6fa; 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: d66700f918b4…, the proof's receipt sha256: d66700f918b45590984f3b0c72ddde1fdd4f09615a8974ee317147b0bd96ca0c; 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 157

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

Holds if: near-t2's record says confirmed

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