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

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

Run · verification · program 6

Run 53

The enclave's verification of commit 20'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) · lowcc52c19a1230…, tag of slot 0: cc52c19a12305290fa0b15741d08f4ec325bacf4242cdef37f4b153e13c33e51

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

e51759c61d379da5…

Request sha256

b4b3647b4c0124bd…

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

Output sha256

84581c9336872239…

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-04 16:20:40 UTC7KduoN6W…

Answered

2026-11-04 16:20:54 UTC14 s after it was requested7KduoN6W…

Commit

Commit 20

Program

Program 6round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

judge-1-p6.practice.antibody.testnet the recorded run's practice try

Violationvault keeps its ether · low

receipt e51759c61d37…

Timeline

Every step is a NEAR transaction, timed by block from commit 20's block.

0.0 s (the commit's block)
Committed
A sealed proof and a 0.0001 wNEAR bond, by the recorded run's practice try (judge-1-p6.practice.antibody.testnet).
L9wQ6bJi…, NEAR transaction: L9wQ6bJiSore1NN2TzsnPDbLcfevZt7K5xt6AqnWtmc, opens an explorer in a new tab2026-11-0416:20:38 UTC · block 276,218,760
+1.8 s after the commit's block
Revealed · run 53 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 b4b3647b4c01…, request sha256: b4b3647b4c0124bd471618664aef8e82fcc793e8a597f07d7de5423722a99d84). 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 e51759c61d37…, receipt sha256: e51759c61d379da5947f1d38291b0efa4bd0d90634a72d9411bd9eda4fd119df. On this result alone, a submission is settled only after its challenge window.

Delivered in 7KduoN6W…, NEAR transaction: 7KduoN6WrLrkPKK6hc1NAWKMmeJqfac9MBt5oi7Ma2DH, opens an explorer in a new tab

Check it yourself

antibody status --run 53

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

{
  "commit": 20,
  "id": 53,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1793809254,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "201a3e60379106cf6c122f929ab3dc5d3132315c69489d51117bb3ea8fc9469f6f9eb480e15729bb275a3a7cd1d32b0962d865ebc286702eabb49fa0"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "cc52c19a12305290fa0b15741d08f4ec325bacf4242cdef37f4b153e13c33e51"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "e51759c61d379da5947f1d38291b0efa4bd0d90634a72d9411bd9eda4fd119df"
      },
      "output_sha256": "84581c93368722399fe480c2101fdead2f42d390920ee54c4357365bf3b51831",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 6,
  "request_sha256": "b4b3647b4c0124bd471618664aef8e82fcc793e8a597f07d7de5423722a99d84",
  "round": 0,
  "signer": "judge-1-p6.practice.antibody.testnet",
  "started_at": 1793809240
}

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

Check it yourself

tx 7KduoN6WrL… · NEAR archival RPC

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

outlayer-verify tx 7KduoN6WrLrkPKK6hc1NAWKMmeJqfac9MBt5oi7Ma2DH

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

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

Check it yourself

What its public values bind

Request sha256: b4b3647b4c01…, the proof's request sha256: b4b3647b4c0124bd471618664aef8e82fcc793e8a597f07d7de5423722a99d84; equals the run's
Run · round · commit: 53 · 0 · 20; equals near-antibody's
Blob sha256: 7216606875ff…, blob sha256: 7216606875ff80d62a1991554d17ab1512fa4a86fd0220d0570bb4ae4f9d215b; bound
Base sha256: bed565c109e1…, base witness sha256: bed565c109e123ddc1b7bce134e15bd8ad95a1bed94d3f6fd2a631e05ab0ed39; bound
Manifest sha256: e275b02e2cb1…, manifest sha256: e275b02e2cb1d88f47b51c2a93ea71a0ae8ba43851d3d6b262bfb690aca5b347; bound
Anchor: block 12063269 on Sepolia; bound
Program key · verifier: bounty.antibody.testnet/6 · 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: e51759c61d37…, the proof's receipt sha256: e51759c61d379da5947f1d38291b0efa4bd0d90634a72d9411bd9eda4fd119df; 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 53

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

Holds if: near-t2's record says confirmed

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