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

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

Run · verification · program 13

Run 172

The enclave's verification of commit 72'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) · low02309fffb4ad…, tag of slot 0: 02309fffb4ad3eb1686ed0411dd7af07b50c1fb4334e2590f9807224160806b4

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

dd68ad633a8f92a2…

Request sha256

1084fe2c8c65ed3c…

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

Output sha256

fee109897d27ad37…

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 00:31:16 UTCFcgMnpje…

Answered

2026-11-09 00:31:31 UTC15 s after it was requestedFcgMnpje…

Commit

Commit 72

Program

Program 13round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

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

Violationvault keeps its ether · low

receipt dd68ad633a8f…

Timeline

Every step is a NEAR transaction, timed by block from commit 72'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 (j3qzkx.practice.antibody.testnet).
H4DNu9Hw…, NEAR transaction: H4DNu9Hw6Rws7nzQR6GiTzNpw9oE9dbqb4b9Pxs3BxsR, opens an explorer in a new tab2026-11-0900:31:14 UTC · block 276,848,578
+1.9 s after the commit's block
Revealed · run 172 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 1084fe2c8c65…, request sha256: 1084fe2c8c65ed3c0558be30c9eba3f982c76b6645c01f554701d50760a2af7c). 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 dd68ad633a8f…, receipt sha256: dd68ad633a8f92a267ef2d2bcd8a03efc40cf1f71beefd9200d52bfc5690ecdc. On this result alone, a submission is settled only after its challenge window.

Delivered in FcgMnpje…, NEAR transaction: FcgMnpjeeNobecJArAtA3WS6vUYpKvbFt39WcjgpD6uV, opens an explorer in a new tab

Check it yourself

antibody status --run 172

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

{
  "commit": 72,
  "id": 172,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794184291,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "9a41d6e344574c7e9ffd19b4e8990b7ed25bcc6bb930f6e5c5986557c529f392e8c3b9de9aab8188a8fe6ef4f50a3b7cc84c9f61274e066f80f77edc"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "02309fffb4ad3eb1686ed0411dd7af07b50c1fb4334e2590f9807224160806b4"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "dd68ad633a8f92a267ef2d2bcd8a03efc40cf1f71beefd9200d52bfc5690ecdc"
      },
      "output_sha256": "fee109897d27ad37e89b4bc5b306f4662ceff5909dd5aba63c793512bdaef154",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 13,
  "request_sha256": "1084fe2c8c65ed3c0558be30c9eba3f982c76b6645c01f554701d50760a2af7c",
  "round": 0,
  "signer": "j3qzkx.practice.antibody.testnet",
  "started_at": 1794184276
}

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

Check it yourself

tx FcgMnpjeeN… · NEAR archival RPC

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

outlayer-verify tx FcgMnpjeeNobecJArAtA3WS6vUYpKvbFt39WcjgpD6uV

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

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

Check it yourself

What its public values bind

Request sha256: 1084fe2c8c65…, the proof's request sha256: 1084fe2c8c65ed3c0558be30c9eba3f982c76b6645c01f554701d50760a2af7c; equals the run's
Run · round · commit: 172 · 0 · 72; equals near-antibody's
Blob sha256: d7b4157cba49…, blob sha256: d7b4157cba49769bb6ca5c6842adaca411bffbd30b9f746b8169b4ded6a47c3b; 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: dd68ad633a8f…, the proof's receipt sha256: dd68ad633a8f92a267ef2d2bcd8a03efc40cf1f71beefd9200d52bfc5690ecdc; 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 172

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

Holds if: near-t2's record says confirmed

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