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

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

Run · verification · program 13

Run 182

The enclave's verification of commit 83'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) · lowf233779d6b38…, tag of slot 0: f233779d6b38b7e1790211d2cde9aee159c8950ae695121e2eef85527cc48914

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

368b987880a6f916…

Request sha256

a791a3100f6b39d0…

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

Output sha256

da0fc4438c67efea…

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-09 00:43:56 UTCFakEGe6d…

Answered

2026-11-09 00:44:09 UTC13 s after it was requestedFakEGe6d…

Commit

Commit 83

Program

Program 13round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

j8vnqd.practice.antibody.testnet a visitor's practice try

Violationvault keeps its ether · low

receipt 368b987880a6…

Timeline

Every step is a NEAR transaction, timed by block from commit 83'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 (j8vnqd.practice.antibody.testnet).
Gp4fNPVi…, NEAR transaction: Gp4fNPViSo4JL7QJGjVg7ayHC9hu4VkSVw9vNEY1YLFV, opens an explorer in a new tab2026-11-0900:43:54 UTC · block 276,849,849
+2.6 s after the commit's block
Revealed · run 182 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 a791a3100f6b…, request sha256: a791a3100f6b39d0659cb16c26948eeca185aabd0c73c1f0a7cf7e8ba406ebda). 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 368b987880a6…, receipt sha256: 368b987880a6f9168c6db11dd807c575f1ee6f37f9b74fb79e2cf0ca9168254f. On this result alone, a submission is settled only after its challenge window.

Delivered in FakEGe6d…, NEAR transaction: FakEGe6dJ53zBnc3nuesFPtjQrUo6uTY8DsSYLTztR6H, opens an explorer in a new tab

Check it yourself

antibody status --run 182

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

{
  "commit": 83,
  "id": 182,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794185049,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "5a3eda1a062451c979ab687a1f706fe8effbfcc30a2d450dec698b4f86a80a992517ceafb29475c91759644ceaccf380dacaadfbab2907fc4d1fddfd"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "f233779d6b38b7e1790211d2cde9aee159c8950ae695121e2eef85527cc48914"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "368b987880a6f9168c6db11dd807c575f1ee6f37f9b74fb79e2cf0ca9168254f"
      },
      "output_sha256": "da0fc4438c67efeac8617588fcfed6d3d7a6868fb4274c9df5641ad7b2f26d46",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 13,
  "request_sha256": "a791a3100f6b39d0659cb16c26948eeca185aabd0c73c1f0a7cf7e8ba406ebda",
  "round": 0,
  "signer": "j8vnqd.practice.antibody.testnet",
  "started_at": 1794185036
}

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

Check it yourself

tx FakEGe6dJ5… · NEAR archival RPC

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

outlayer-verify tx FakEGe6dJ53zBnc3nuesFPtjQrUo6uTY8DsSYLTztR6H

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

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 182

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