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

Run 35 · verification · No violation · Zero-knowledge proof · Antibody

Run · verification · program 5

Run 35

The enclave's verification of commit 15's sealed proof: No violation.

No 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: No violation
Keys: none: no rule broke
Impact: $33.48 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: 0326cfc9b4f8f727…, receipt sha256: 0326cfc9b4f8f727dec761c64a9f9ec0c0db46f9bf6c376526dbd3d8a744ba8d
Request sha256: 6c2bcfd74c9a5595…, request sha256: 6c2bcfd74c9a559532c72ca4ab86ec422c7aea800cc1f85b43a032e209b4d4c4
The SHA-256 of the input near-antibody sent the enclave: its result and its attestation bind to the same bytes.
Output sha256: 5d97c7d852a6fbcb…, output sha256: 5d97c7d852a6fbcbccd32b6c43ac948a245194fad8550581b2412c230431f967
The SHA-256 of the facts near-antibody received: the TDX quote binds it.
Mode extras: none
Started: 2026-11-04 15:47:56 UTC9AFUgQcM…, NEAR transaction: 9AFUgQcMXQng9mysBXfJYJt2RKUTaiHebfhAJDfw1kHN, opens an explorer in a new tab
Answered: 2026-11-04 15:48:09 UTC13 s after it was requested9AFUgQcM…, NEAR transaction: 9AFUgQcMXQng9mysBXfJYJt2RKUTaiHebfhAJDfw1kHN, opens an explorer in a new tab
Commit: Commit 15
Program: Program 5round 0
Paid for by: agent-c.antibody.testnet, account: agent-c.antibody.testnet our fixture agent C

No violationno rule broken

receipt 0326cfc9b4f8…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.001 wNEAR bond, by our fixture agent C (agent-c.antibody.testnet). Nobody, the project included, can read it before its verdict.
4ymAcWJ7…, NEAR transaction: 4ymAcWJ7wAV1tDKArS95uJz3BEeeSmQn6LSk7kJGfx7E, opens an explorer in a new tab2026-11-0415:47:49 UTC · block 276,215,329
+6.6 s after the commit's block
Revealed · run 35 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 6c2bcfd74c9a…, request sha256: 6c2bcfd74c9a559532c72ca4ab86ec422c7aea800cc1f85b43a032e209b4d4c4).

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: No violation, receipt 0326cfc9b4f8…, receipt sha256: 0326cfc9b4f8f727dec761c64a9f9ec0c0db46f9bf6c376526dbd3d8a744ba8d. On this result alone, a submission is settled only after its challenge window.

Delivered in 9AFUgQcM…, NEAR transaction: 9AFUgQcMXQng9mysBXfJYJt2RKUTaiHebfhAJDfw1kHN, opens an explorer in a new tab

Check it yourself

antibody status --run 35

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

{
  "commit": 15,
  "id": 35,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1793807289,
      "facts": {
        "extra": "None",
        "impact_usd_micro": "33480361",
        "keys": [],
        "kind": "NoViolation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "0326cfc9b4f8f727dec761c64a9f9ec0c0db46f9bf6c376526dbd3d8a744ba8d"
      },
      "output_sha256": "5d97c7d852a6fbcbccd32b6c43ac948a245194fad8550581b2412c230431f967",
      "tier": "T1"
    }
  },
  "payer": "agent-c.antibody.testnet",
  "program": 5,
  "request_sha256": "6c2bcfd74c9a559532c72ca4ab86ec422c7aea800cc1f85b43a032e209b4d4c4",
  "round": 0,
  "signer": "agent-c.antibody.testnet",
  "started_at": 1793807276
}

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

Check it yourself

tx 9AFUgQcMXQ… · NEAR archival RPC

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

outlayer-verify tx 9AFUgQcMXQng9mysBXfJYJt2RKUTaiHebfhAJDfw1kHN

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

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

Check it yourself

What its public values bind

Request sha256: 6c2bcfd74c9a…, the proof's request sha256: 6c2bcfd74c9a559532c72ca4ab86ec422c7aea800cc1f85b43a032e209b4d4c4; equals the run's
Run · round · commit: 35 · 0 · 15; equals near-antibody's
Blob sha256: 598272a3d161…, blob sha256: 598272a3d1616a306140711305c227f5231357551d6fe0aac598fa29c31c8dce; 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: 0326cfc9b4f8…, the proof's receipt sha256: 0326cfc9b4f8f727dec761c64a9f9ec0c0db46f9bf6c376526dbd3d8a744ba8d; equals the enclave's
Kind: NoViolation; equals the enclave's
Slots (severity): none; 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 35

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

Holds if: near-t2's record says confirmed

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