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

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

Run · verification · program 10

Run 92

The enclave's verification of commit 54'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) · lowe785acba2b52…, tag of slot 0: e785acba2b52668fee0a29acc2dd146b01f367b798636fdcacd66c15b4502924

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

4fed54a6857db13a…

Request sha256

1850f35205318014…

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

Output sha256

e745d6b4091270c0…

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 13:06:41 UTCFVhbiDA3…

Answered

2026-11-08 13:06:54 UTC13 s after it was requestedFVhbiDA3…

Commit

Commit 54

Program

Program 10round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

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

Violationvault keeps its ether · low

receipt 4fed54a6857d…

Timeline

Every step is a NEAR transaction, timed by block from commit 54'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 (scrn8k2qz1108.practice.antibody.testnet).
AWgjGeSU…, NEAR transaction: AWgjGeSUyyXf7hAfa5tmwpnTop1jcKko2TRruuiYLyYF, opens an explorer in a new tab2026-11-0813:06:33 UTC · block 276,779,624
+8.5 s after the commit's block
Revealed · run 92 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 1850f3520531…, request sha256: 1850f3520531801417440de14658ce17aaa546bdde73227286610be19ebf47e4). 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 4fed54a6857d…, receipt sha256: 4fed54a6857db13aa3c957b7763f8a6b27a1d94aeef5b5ab3756eb8fc5fee6c7. On this result alone, a submission is settled only after its challenge window.

Delivered in FVhbiDA3…, NEAR transaction: FVhbiDA3PRzo3njcMEquuppaJg64MzFShMxw8sxypgWe, opens an explorer in a new tab

Check it yourself

antibody status --run 92

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

{
  "commit": 54,
  "id": 92,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794143214,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "1df3843d2fa7257b7ab135c1f3a108c836878719a27da065df76c72747c089ab354400bbf8523e2c76d6237e46641ed6445307166c58ae33584cd907"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "e785acba2b52668fee0a29acc2dd146b01f367b798636fdcacd66c15b4502924"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "4fed54a6857db13aa3c957b7763f8a6b27a1d94aeef5b5ab3756eb8fc5fee6c7"
      },
      "output_sha256": "e745d6b4091270c09f5f78bb63d7ac323dae5d0be1abcac7b3d89ea03b34e0e5",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 10,
  "request_sha256": "1850f3520531801417440de14658ce17aaa546bdde73227286610be19ebf47e4",
  "round": 0,
  "signer": "scrn8k2qz1108.practice.antibody.testnet",
  "started_at": 1794143201
}

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

Check it yourself

tx FVhbiDA3PR… · NEAR archival RPC

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

outlayer-verify tx FVhbiDA3PRzo3njcMEquuppaJg64MzFShMxw8sxypgWe

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

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

Check it yourself

What its public values bind

Request sha256: 1850f3520531…, the proof's request sha256: 1850f3520531801417440de14658ce17aaa546bdde73227286610be19ebf47e4; equals the run's
Run · round · commit: 92 · 0 · 54; equals near-antibody's
Blob sha256: 5a0e8b4630da…, blob sha256: 5a0e8b4630da41b55d6c7d32bd9c0624a850c9673be042a283648195ae5ed099; 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: 4fed54a6857d…, the proof's receipt sha256: 4fed54a6857db13aa3c957b7763f8a6b27a1d94aeef5b5ab3756eb8fc5fee6c7; 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 92

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

Holds if: near-t2's record says confirmed

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