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

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

Run · verification · program 14

Run 186

The enclave's verification of commit 86'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) · lowc5f4deaffcd5…, tag of slot 0: c5f4deaffcd593be8666be714a6fe573b0bae219c67273cfdc69f3c24f189215

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

10e5d5abc6b20397…

Request sha256

a5034160278fb7fd…

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

Output sha256

7720c77bfc54bf0b…

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:30:40 UTC5t8VTxs9…

Answered

2026-11-09 01:30:55 UTC15 s after it was requested5t8VTxs9…

Commit

Commit 86

Program

Program 14round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

judge-2-p14.practice.antibody.testnet our check of a fresh practice program

Violationvault keeps its ether · low

receipt 10e5d5abc6b2…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.0001 wNEAR bond, by our check of a fresh practice program (judge-2-p14.practice.antibody.testnet).
DHsbfc7P…, NEAR transaction: DHsbfc7PzYwBeD4NokrUyQtRtc2cVEa438rc4zNRnLDa, opens an explorer in a new tab2026-11-0901:30:39 UTC · block 276,854,498
+1.8 s after the commit's block
Revealed · run 186 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 a5034160278f…, request sha256: a5034160278fb7fd05123228dbe791f74305bdedc921c5b8b3963385f175d346). 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 10e5d5abc6b2…, receipt sha256: 10e5d5abc6b2039759aa8f3ae8c365391937d73a6baf43a5abe074d716756357. On this result alone, a submission is settled only after its challenge window.

Delivered in 5t8VTxs9…, NEAR transaction: 5t8VTxs9d5vQ22oGu5oN16x6jHyFEzhMaJw5i8dUyRpj, opens an explorer in a new tab

Check it yourself

antibody status --run 186

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

{
  "commit": 86,
  "id": 186,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794187855,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "15bda368a57f165fa859c93528e4d4a38f71e635cbaa8fa2c07e2779937896a77c91d7ec4e1b1a3164e03e7a85c3dec7316740b9ecdac27ba5b644dd"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "c5f4deaffcd593be8666be714a6fe573b0bae219c67273cfdc69f3c24f189215"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "10e5d5abc6b2039759aa8f3ae8c365391937d73a6baf43a5abe074d716756357"
      },
      "output_sha256": "7720c77bfc54bf0bcf30243e35fa431893efb767fbec3dd7283dd5327cc9968b",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 14,
  "request_sha256": "a5034160278fb7fd05123228dbe791f74305bdedc921c5b8b3963385f175d346",
  "round": 0,
  "signer": "judge-2-p14.practice.antibody.testnet",
  "started_at": 1794187840
}

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

Check it yourself

tx 5t8VTxs9d5… · NEAR archival RPC

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

outlayer-verify tx 5t8VTxs9d5vQ22oGu5oN16x6jHyFEzhMaJw5i8dUyRpj

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

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 186

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