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

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

Run · verification · program 5

Run 33

The enclave's verification of commit 13's sealed proof: Violation of the solvency 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 (solvency) · critical325703227266…, tag of slot 0: 325703227266ea4d3828142c490819fbc957bef5065a5ce0daeb03ee75242199

Impact

$462,931.85 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

0ea67c6a56b964c4…

Request sha256

c348b67ec9a15c29…

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

Output sha256

c0c46c1444c520cd…

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 15:42:17 UTC8yEJyYXg…

Answered

2026-11-04 15:42:29 UTC12 s after it was requested8yEJyYXg…

Commit

Commit 13

Program

Program 5round 0

Paid for by

agent-a.antibody.testnet our fixture agent A

Violationsolvency · critical

receipt 0ea67c6a56b9…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.001 wNEAR bond, by our fixture agent A (agent-a.antibody.testnet). Nobody, the project included, can read it before its verdict.
CynCsx8P…, NEAR transaction: CynCsx8PNsFAYnYp6Zk5HjpSg3fWUrHSKfJ9CD9HQ3nP, opens an explorer in a new tab2026-11-0415:42:11 UTC · block 276,214,742
+6.0 s after the commit's block
Revealed · run 33 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 c348b67ec9a1…, request sha256: c348b67ec9a15c29e066fa0d3933944be77336a394dce17b70d95554480afd86).

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 0ea67c6a56b9…, receipt sha256: 0ea67c6a56b964c4a8ef66861c89d56e99e0428836316d727f9d3dcea3dca2ee. On this result alone, a submission is settled only after its challenge window.

Delivered in 8yEJyYXg…, NEAR transaction: 8yEJyYXgz34BJWCTPLVnvq13PLW15oBx8uzkMkopc4DY, opens an explorer in a new tab

Check it yourself

antibody status --run 33

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

{
  "commit": 13,
  "id": 33,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1793806949,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "eaf95f64efb4fc0ce8841dd1acca5bacec824280ee5fde7e85256b6dfa5bf69c736292a3799cafc6b51fc2df27bea6b856c34d515219a2fc81418efe"
          }
        },
        "impact_usd_micro": "462931853867",
        "keys": [
          {
            "slot": 0,
            "tag": "325703227266ea4d3828142c490819fbc957bef5065a5ce0daeb03ee75242199"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "0ea67c6a56b964c4a8ef66861c89d56e99e0428836316d727f9d3dcea3dca2ee"
      },
      "output_sha256": "c0c46c1444c520cd9ce18c915309cbd070868f6386c3643b1bf8b42d43ee2c7f",
      "tier": "T1"
    }
  },
  "payer": "agent-a.antibody.testnet",
  "program": 5,
  "request_sha256": "c348b67ec9a15c29e066fa0d3933944be77336a394dce17b70d95554480afd86",
  "round": 0,
  "signer": "agent-a.antibody.testnet",
  "started_at": 1793806937
}

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

Check it yourself

tx 8yEJyYXgz3… · NEAR archival RPC

antibody tee check --request-id 8839

outlayer-verify job 8839 --network testnet

Request 8839, as t1-collateral-2026-11-06.json records it; the button reads it from the transaction itself.

outlayer-verify tx 8yEJyYXgz34BJWCTPLVnvq13PLW15oBx8uzkMkopc4DY

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

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

Check it yourself

What its public values bind

Request sha256: c348b67ec9a1…, the proof's request sha256: c348b67ec9a15c29e066fa0d3933944be77336a394dce17b70d95554480afd86; equals the run's
Run · round · commit: 33 · 0 · 13; equals near-antibody's
Blob sha256: 0669dce31905…, blob sha256: 0669dce319052f3db3a4b1377040a3c4842b528998ec3e1f92a1cab3e1ce6ef2; bound
Base sha256: 200cc7e636e7…, base witness sha256: 200cc7e636e7bd4fe9056cd2d4707d1eccadc3f656d4e9e3d61e68c9ffaba621; bound
Manifest sha256: be42d0c87d99…, manifest sha256: be42d0c87d995331f0b3f9f912cc3aad8537eedc56adc39bc088c2dcaf079518; bound
Anchor: block 12063269 on Sepolia; bound
Program key · verifier: bounty.antibody.testnet/5 · 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: 0ea67c6a56b9…, the proof's receipt sha256: 0ea67c6a56b964c4a8ef66861c89d56e99e0428836316d727f9d3dcea3dca2ee; equals the enclave's
Kind: Violation; equals the enclave's
Slots (severity): 0 critical; 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 33

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

Holds if: near-t2's record says confirmed

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