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

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

Run · verification · program 14

Run 188

The enclave's verification of commit 87'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) · low9ed1f29229b6…, tag of slot 0: 9ed1f29229b6b302bc067c67ce98e00b67f8196b3c52dbf2e54267efb8dacfa6

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

94111c894430de51…

Request sha256

2c38db2c01ff8479…

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

Output sha256

fd261850ea8df0e7…

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 01:33:12 UTC5fCSmCsA…

Answered

2026-11-09 01:33:27 UTC15 s after it was requested5fCSmCsA…

Commit

Commit 87

Program

Program 14round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

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

Violationvault keeps its ether · low

receipt 94111c894430…

Timeline

Every step is a NEAR transaction, timed by block from commit 87'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 (s062a0432.practice.antibody.testnet).
4muWwdAn…, NEAR transaction: 4muWwdAnqCf81etw6TiXBX9WRWXPCs43uNyQVKyLBrNo, opens an explorer in a new tab2026-11-0901:33:10 UTC · block 276,854,751
+2.3 s after the commit's block
Revealed · run 188 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 2c38db2c01ff…, request sha256: 2c38db2c01ff84792c7a307d5888dc60c9bcf953e5c26b4408a0a7b32be554b9). 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 94111c894430…, receipt sha256: 94111c894430de510613a102f19267af2cb717ee2b0fe196e20fd104a42b941e. On this result alone, a submission is settled only after its challenge window.

Delivered in 5fCSmCsA…, NEAR transaction: 5fCSmCsAh8Eyj1yUtiSc1JcFEjSyo2bdz8NNrmGhQd2T, opens an explorer in a new tab

Check it yourself

antibody status --run 188

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

{
  "commit": 87,
  "id": 188,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794188007,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "bcdcd4ecdf19f78ab0a64becd2af9c75a7404e79e26d58d1ab9bfacf07de27a27c765a49cbdcfe7fc144f7316d11f109374ec53dee1942e511a57ac2"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "9ed1f29229b6b302bc067c67ce98e00b67f8196b3c52dbf2e54267efb8dacfa6"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "94111c894430de510613a102f19267af2cb717ee2b0fe196e20fd104a42b941e"
      },
      "output_sha256": "fd261850ea8df0e78fb90525fefc81ce17232bb1384b35371f03c83cb1a5626b",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 14,
  "request_sha256": "2c38db2c01ff84792c7a307d5888dc60c9bcf953e5c26b4408a0a7b32be554b9",
  "round": 0,
  "signer": "s062a0432.practice.antibody.testnet",
  "started_at": 1794187992
}

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

Check it yourself

tx 5fCSmCsAh8… · NEAR archival RPC

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

outlayer-verify tx 5fCSmCsAh8Eyj1yUtiSc1JcFEjSyo2bdz8NNrmGhQd2T

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

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 188

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