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

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

Run · verification · program 5

Run 36

The enclave's verification of commit 16'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

$6,375.60 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

fa62fbea3e9ea80f…

Request sha256

83e954f00a028710…

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

Output sha256

6fbc1aa2dd381043…

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:48:22 UTC46YmqNdd…

Answered

2026-11-04 15:48:35 UTC13 s after it was requested46YmqNdd…

Commit

Commit 16

Program

Program 5round 0

Paid for by

agent-d.antibody.testnet our fixture agent D

Violationsolvency · critical

receipt fa62fbea3e9e…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.001 wNEAR bond, by our fixture agent D (agent-d.antibody.testnet). Nobody, the project included, can read it before its verdict.
6E5i332d…, NEAR transaction: 6E5i332dtV5a1kjgwyNBUkpSS9N5VEDv7i2Wj5JeAuXT, opens an explorer in a new tab2026-11-0415:48:16 UTC · block 276,215,374
+5.9 s after the commit's block
Revealed · run 36 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 83e954f00a02…, request sha256: 83e954f00a028710a15249ca2a13982fae06007f1489fe8ad1d83a1a5d305592).

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

Delivered in 46YmqNdd…, NEAR transaction: 46YmqNddvWgw55MBn5JcGXVGZ4cHkyzsojig6tLFxJhZ, opens an explorer in a new tab

Check it yourself

antibody status --run 36

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

{
  "commit": 16,
  "id": 36,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1793807315,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "7cbdc08b3c36dddf07bab948298d98ec37437f3500101817604ebd514d16cf104f9b5e355489b590c5f8e603c8ec3c182d94a35371235e0cdccf5c90"
          }
        },
        "impact_usd_micro": "6375600000",
        "keys": [
          {
            "slot": 0,
            "tag": "325703227266ea4d3828142c490819fbc957bef5065a5ce0daeb03ee75242199"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "fa62fbea3e9ea80fc38a8c5411b7041948e26add0c98efe501eafeec318d7c98"
      },
      "output_sha256": "6fbc1aa2dd3810437149a1743cf8878fc0fb8c8050ef2ea8b69142cdd9cd328e",
      "tier": "T1"
    }
  },
  "payer": "agent-d.antibody.testnet",
  "program": 5,
  "request_sha256": "83e954f00a028710a15249ca2a13982fae06007f1489fe8ad1d83a1a5d305592",
  "round": 0,
  "signer": "agent-d.antibody.testnet",
  "started_at": 1793807302
}

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

Check it yourself

tx 46YmqNddvW… · NEAR archival RPC

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

outlayer-verify tx 46YmqNddvWgw55MBn5JcGXVGZ4cHkyzsojig6tLFxJhZ

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

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

Check it yourself

What its public values bind

Request sha256: 83e954f00a02…, the proof's request sha256: 83e954f00a028710a15249ca2a13982fae06007f1489fe8ad1d83a1a5d305592; equals the run's
Run · round · commit: 36 · 0 · 16; equals near-antibody's
Blob sha256: d896c7f7e273…, blob sha256: d896c7f7e273186f68d4ac96141111036df1a48abb637680d41e9de55ced6e34; 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: fa62fbea3e9e…, the proof's receipt sha256: fa62fbea3e9ea80fc38a8c5411b7041948e26add0c98efe501eafeec318d7c98; 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 36

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

Holds if: near-t2's record says confirmed

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