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

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

Run · verification · program 14

Run 222

The enclave's verification of commit 101'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) · lowe20de9c41612…, tag of slot 0: e20de9c416129c5c07eee6821e8c8b47af77d793e92788e7ef090470c8b7afd6

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

b71d5707e57dfe5a…

Request sha256

93e0fde387ea3eb0…

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

Output sha256

6d09a26dedc81c76…

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-09 06:32:31 UTCBgtbzxxu…

Answered

2026-11-09 06:32:45 UTC14 s after it was requestedBgtbzxxu…

Commit

Commit 101

Program

Program 14round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

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

Violationvault keeps its ether · low

receipt b71d5707e57d…

Timeline

Every step is a NEAR transaction, timed by block from commit 101'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 (film1109.practice.antibody.testnet).
7UajXN2w…, NEAR transaction: 7UajXN2wmD9RFAHc5x3C59K54EXx4iQ2HLQpCkvp5HzJ, opens an explorer in a new tab2026-11-0906:32:29 UTC · block 276,884,392
+2.3 s after the commit's block
Revealed · run 222 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 93e0fde387ea…, request sha256: 93e0fde387ea3eb08bdbe1e285a7828b541a57fea803678e225d966ab7d06939). 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 b71d5707e57d…, receipt sha256: b71d5707e57dfe5a0416be1e46fffefba55b8c9f52808fac68e367b5473f7a3a. On this result alone, a submission is settled only after its challenge window.

Delivered in Bgtbzxxu…, NEAR transaction: BgtbzxxuADMEqc7SYkK4h63FdHgrSJg3USkEyQtto8Fi, opens an explorer in a new tab

Check it yourself

antibody status --run 222

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

{
  "commit": 101,
  "id": 222,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794205965,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "36142857f12e4930941d27dba25aff3e469b4c088cbbc9b08642ca5275a0e788839a598bf3f9597f821feb5d2cae44b3cb86c357b8eac5906bbac31c"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "e20de9c416129c5c07eee6821e8c8b47af77d793e92788e7ef090470c8b7afd6"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "b71d5707e57dfe5a0416be1e46fffefba55b8c9f52808fac68e367b5473f7a3a"
      },
      "output_sha256": "6d09a26dedc81c76972421a539674232c15d0df5f7914198b57646cdae0c797f",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 14,
  "request_sha256": "93e0fde387ea3eb08bdbe1e285a7828b541a57fea803678e225d966ab7d06939",
  "round": 0,
  "signer": "film1109.practice.antibody.testnet",
  "started_at": 1794205951
}

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

Check it yourself

tx BgtbzxxuAD… · NEAR archival RPC

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

outlayer-verify tx BgtbzxxuADMEqc7SYkK4h63FdHgrSJg3USkEyQtto8Fi

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

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

Check it yourself

What its public values bind

Request sha256: 93e0fde387ea…, the proof's request sha256: 93e0fde387ea3eb08bdbe1e285a7828b541a57fea803678e225d966ab7d06939; equals the run's
Run · round · commit: 222 · 0 · 101; equals near-antibody's
Blob sha256: e0c106dea726…, blob sha256: e0c106dea726c909fc9245d4200a95da1ddb6a108439a6b13b8f6ea5968df605; bound
Base sha256: d9a1bcaad130…, base witness sha256: d9a1bcaad13099ea119b68cbd34e4ee1dc1426ab99d5956435d304e9a3728f4b; bound
Manifest sha256: 5561196dd6fe…, manifest sha256: 5561196dd6fe0e3f4e1a1e3c78759af72226ab53296a2a124a6a0d6e9adc4e67; bound
Anchor: block 12094137 on Sepolia; bound
Program key · verifier: bounty.antibody.testnet/14 · 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: b71d5707e57d…, the proof's receipt sha256: b71d5707e57dfe5a0416be1e46fffefba55b8c9f52808fac68e367b5473f7a3a; 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 222

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

Holds if: near-t2's record says confirmed

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