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

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

Run · verification · program 13

Run 175

The enclave's verification of commit 75'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: $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: d4552aa7bce3f97e…, receipt sha256: d4552aa7bce3f97ebe335ed253aac9fb58f2bee3b626f6aa897e2f85831e7353
Request sha256: 5cce5352a1f0bea1…, request sha256: 5cce5352a1f0bea1ab236a714bb46b6d225691f13039b280a4ef2e57eb25cc54
The SHA-256 of the input near-antibody sent the enclave: its result and its attestation bind to the same bytes.
Output sha256: b85a9c198d8eb335…, output sha256: b85a9c198d8eb3354a6d478aac17a3646222dda9a5861e50d6de908adf1769a5
The SHA-256 of the facts near-antibody received: the TDX quote binds it.
Mode extras: none
Started: 2026-11-09 00:32:41 UTC14FW1UKB…, NEAR transaction: 14FW1UKBvhxUPt8kcccmLB6WCNcsmVrRQ3jXiVcovEEG, opens an explorer in a new tab
Answered: 2026-11-09 00:32:54 UTC13 s after it was requested14FW1UKB…, NEAR transaction: 14FW1UKBvhxUPt8kcccmLB6WCNcsmVrRQ3jXiVcovEEG, opens an explorer in a new tab
Commit: Commit 75
Program: Program 13round 0
Paid for by: practice.antibody.testnet, account: practice.antibody.testnet the practice vending contract
Signed by: j3hqvw.practice.antibody.testnet, account: j3hqvw.practice.antibody.testnet a visitor's practice try

No violationno rule broken

receipt d4552aa7bce3…

Timeline

Every step is a NEAR transaction, timed by block from commit 75'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 (j3hqvw.practice.antibody.testnet).
DVFVjdn7…, NEAR transaction: DVFVjdn7KVtpwutj2UjEWjfMrdmd2b5J93adQ9YbmNye, opens an explorer in a new tab2026-11-0900:32:38 UTC · block 276,848,726
+2.3 s after the commit's block
Revealed · run 175 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 5cce5352a1f0…, request sha256: 5cce5352a1f0bea1ab236a714bb46b6d225691f13039b280a4ef2e57eb25cc54). 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: No violation, receipt d4552aa7bce3…, receipt sha256: d4552aa7bce3f97ebe335ed253aac9fb58f2bee3b626f6aa897e2f85831e7353. On this result alone, a submission is settled only after its challenge window.

Delivered in 14FW1UKB…, NEAR transaction: 14FW1UKBvhxUPt8kcccmLB6WCNcsmVrRQ3jXiVcovEEG, opens an explorer in a new tab

Check it yourself

antibody status --run 175

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

{
  "commit": 75,
  "id": 175,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794184374,
      "facts": {
        "extra": "None",
        "impact_usd_micro": "0",
        "keys": [],
        "kind": "NoViolation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "d4552aa7bce3f97ebe335ed253aac9fb58f2bee3b626f6aa897e2f85831e7353"
      },
      "output_sha256": "b85a9c198d8eb3354a6d478aac17a3646222dda9a5861e50d6de908adf1769a5",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 13,
  "request_sha256": "5cce5352a1f0bea1ab236a714bb46b6d225691f13039b280a4ef2e57eb25cc54",
  "round": 0,
  "signer": "j3hqvw.practice.antibody.testnet",
  "started_at": 1794184361
}

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

Check it yourself

tx 14FW1UKBvh… · NEAR archival RPC

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

outlayer-verify tx 14FW1UKBvhxUPt8kcccmLB6WCNcsmVrRQ3jXiVcovEEG

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

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

Check it yourself

What its public values bind

Request sha256: 5cce5352a1f0…, the proof's request sha256: 5cce5352a1f0bea1ab236a714bb46b6d225691f13039b280a4ef2e57eb25cc54; equals the run's
Run · round · commit: 175 · 0 · 75; equals near-antibody's
Blob sha256: 6a980ba295be…, blob sha256: 6a980ba295be162f091fe540a51835cf755636b708853da92443259da9c70f1a; 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: d4552aa7bce3…, the proof's receipt sha256: d4552aa7bce3f97ebe335ed253aac9fb58f2bee3b626f6aa897e2f85831e7353; 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 175

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

Holds if: near-t2's record says confirmed

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