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

Run 91 · verification · Violation · Attested on NEAR · Antibody

Run · verification · program 10

Run 91

The enclave's verification of commit 53's sealed proof: Violation of the “vault keeps its ether” rule.

ViolationAttested on NEAR

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) · low55db494bc9bf…, tag of slot 0: 55db494bc9bf545b117d8bced5a9cb4fa1ba5e6680f03af357c868e2011f7a55

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

Attested on NEAR

Receipt sha256

d407e1e5bd908e31…

Request sha256

6ba28cafafe9eec7…

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

Output sha256

2c8c0e4fc4d9e5a2…

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-08 09:28:58 UTCCwch9FY1…

Answered

2026-11-08 09:29:12 UTC14 s after it was requestedCwch9FY1…

Commit

Commit 53

Program

Program 10round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

m11080919-05.practice.antibody.testnet a measured agent run (docs/agent-runs.md)

Violationvault keeps its ether · low

receipt d407e1e5bd90…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.0001 wNEAR bond, by a measured agent run (docs/agent-runs.md) (m11080919-05.practice.antibody.testnet).
7bMBXF4V…, NEAR transaction: 7bMBXF4VbbA38AGJtPMJBNVn1UKqvr9hVxMMQzHpExGF, opens an explorer in a new tab2026-11-0809:28:55 UTC · block 276,757,442
+2.4 s after the commit's block
Revealed · run 91 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 6ba28cafafe9…, request sha256: 6ba28cafafe9eec790613c3f9e050a98f1ccafffdc74d7474d7188d6f1ee797b). 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 d407e1e5bd90…, receipt sha256: d407e1e5bd908e31e2c8680030a5921894427d6df50e4be56bcb8a8faacb6598. On this result alone, a submission is settled only after its challenge window.

Delivered in Cwch9FY1…, NEAR transaction: Cwch9FY1NLAbYcKSMnyUu3spBVTqEPLbkiLUtZXK3HiE, opens an explorer in a new tab

Check it yourself

antibody status --run 91

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

{
  "commit": 53,
  "id": 91,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794130152,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "b6a2a7919ece0ef1f5440a801763c323de216151eaee1ab8eb919193ffb62096aad24f1716536311aef07eb9b74443805d93f33426a0fd3c88fd4778"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "55db494bc9bf545b117d8bced5a9cb4fa1ba5e6680f03af357c868e2011f7a55"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "d407e1e5bd908e31e2c8680030a5921894427d6df50e4be56bcb8a8faacb6598"
      },
      "output_sha256": "2c8c0e4fc4d9e5a291508e2dd8ecbc3da833099a3979062d2733890b7c9d8c58",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 10,
  "request_sha256": "6ba28cafafe9eec790613c3f9e050a98f1ccafffdc74d7474d7188d6f1ee797b",
  "round": 0,
  "signer": "m11080919-05.practice.antibody.testnet",
  "started_at": 1794130138
}

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

Check it yourself

tx Cwch9FY1NL… · NEAR archival RPC

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

outlayer-verify tx Cwch9FY1NLAbYcKSMnyUu3spBVTqEPLbkiLUtZXK3HiE

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

Holds if: the run is attested: its quote was verified on NEAR

Zero-knowledge proofno record yet

A zero-knowledge proof of the verdict

near-t2 has no record of this run yet. A zero-knowledge proof re-runs a disclosed proof, so it follows disclosure, or a published key; a practice try sealed with the public practice key is proven by our prover service with nothing handed over.

Check it yourself

antibody zk status --run 91

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