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

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

Run · verification · program 13

Run 152

The enclave's verification of commit 66'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) · low3f12a6a81973…, tag of slot 0: 3f12a6a819737feed8b50e34f544c36191802bb12fef2118a6d0dc6cef14cc4e

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

8134e5c1c74ee194…

Request sha256

80bf63b5595006a4…

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

Output sha256

7e8eddcbd4dc0e87…

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:23:08 UTCDNLBidzY…

Answered

2026-11-08 22:23:21 UTC13 s after it was requestedDNLBidzY…

Commit

Commit 66

Program

Program 13round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

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

Violationvault keeps its ether · low

receipt 8134e5c1c74e…

Timeline

Every step is a NEAR transaction, timed by block from commit 66'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 (j4nqsy.practice.antibody.testnet).
6tmsQRXk…, NEAR transaction: 6tmsQRXkcHbc1hAc5ZLhreDXusHeG2u2XW5HBUnLiNEm, opens an explorer in a new tab2026-11-0822:23:04 UTC · block 276,835,828
+4.2 s after the commit's block
Revealed · run 152 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 80bf63b55950…, request sha256: 80bf63b5595006a44912b0d50a4672e508a9258fd28a1761a9de83ffbd0a7346). 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 8134e5c1c74e…, receipt sha256: 8134e5c1c74ee1946319ed1696461a676e9468078f1071f26489cf81528593ea. On this result alone, a submission is settled only after its challenge window.

Delivered in DNLBidzY…, NEAR transaction: DNLBidzYqgTJrPv7tjNnFMsfQebvDu59vqs6938UqV5w, opens an explorer in a new tab

Check it yourself

antibody status --run 152

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

{
  "commit": 66,
  "id": 152,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794176601,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "3e5cd02441400f7bc21ce5399e91ef6de3fb4d2f63559e4f711354cd8ad4f45f477cd085d6aeb2132f4c920fff44c539e7f7e2b7dc67a1049f5be282"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "3f12a6a819737feed8b50e34f544c36191802bb12fef2118a6d0dc6cef14cc4e"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "8134e5c1c74ee1946319ed1696461a676e9468078f1071f26489cf81528593ea"
      },
      "output_sha256": "7e8eddcbd4dc0e870d6a57535e9d91dbab4c5372eb5b98b9bc7c0f02c435c575",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 13,
  "request_sha256": "80bf63b5595006a44912b0d50a4672e508a9258fd28a1761a9de83ffbd0a7346",
  "round": 0,
  "signer": "j4nqsy.practice.antibody.testnet",
  "started_at": 1794176588
}

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

Check it yourself

tx DNLBidzYqg… · NEAR archival RPC

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

outlayer-verify tx DNLBidzYqgTJrPv7tjNnFMsfQebvDu59vqs6938UqV5w

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

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

Check it yourself

What its public values bind

Request sha256: 80bf63b55950…, the proof's request sha256: 80bf63b5595006a44912b0d50a4672e508a9258fd28a1761a9de83ffbd0a7346; equals the run's
Run · round · commit: 152 · 0 · 66; equals near-antibody's
Blob sha256: 7cf998b994fd…, blob sha256: 7cf998b994fd85c58258e57526f87c5ba346cf58b9f75379b9d6ddad14e5730b; 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: 8134e5c1c74e…, the proof's receipt sha256: 8134e5c1c74ee1946319ed1696461a676e9468078f1071f26489cf81528593ea; 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 152

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

Holds if: near-t2's record says confirmed

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