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

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

Run · verification · program 13

Run 181

The enclave's verification of commit 82'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) · low0b0e6beae181…, tag of slot 0: 0b0e6beae181ed57dfcc97c2d0c9547139c950136710cdaae2c9bb4e490dc5a2

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

697429c59ed030b0…

Request sha256

b255d84b88072286…

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

Output sha256

3cc66ed64120f1fb…

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:42:32 UTC8WgdjVrY…

Answered

2026-11-09 00:42:48 UTC16 s after it was requested8WgdjVrY…

Commit

Commit 82

Program

Program 13round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

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

Violationvault keeps its ether · low

receipt 697429c59ed0…

Timeline

Every step is a NEAR transaction, timed by block from commit 82'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 (j5qxkv.practice.antibody.testnet).
BaoYUU8G…, NEAR transaction: BaoYUU8Gd2gZcKhw7RQskfuEawpssaGZyfdAnpPixMvG, opens an explorer in a new tab2026-11-0900:42:30 UTC · block 276,849,703
+2.5 s after the commit's block
Revealed · run 181 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 b255d84b8807…, request sha256: b255d84b88072286b02fff840146a6e8202bb0466348e13176e3ed2fccf2058e). 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 697429c59ed0…, receipt sha256: 697429c59ed030b06f6408eaab9775e43bce8bde5df6839a0cb610c02d2cf5a3. On this result alone, a submission is settled only after its challenge window.

Delivered in 8WgdjVrY…, NEAR transaction: 8WgdjVrY3hNzcLYtC8ZmodJKuFmxVbT2hxZEG4nmHe5d, opens an explorer in a new tab

Check it yourself

antibody status --run 181

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

{
  "commit": 82,
  "id": 181,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794184968,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "d3a4fcd85ae9023bc22a2363bdca7b5595abae2f667b28a965032763500c3f3a3e2e0be16a343531ad51277e6420f2108f6b9505b5c1f79714b30421"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "0b0e6beae181ed57dfcc97c2d0c9547139c950136710cdaae2c9bb4e490dc5a2"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "697429c59ed030b06f6408eaab9775e43bce8bde5df6839a0cb610c02d2cf5a3"
      },
      "output_sha256": "3cc66ed64120f1fb61be13715a5b5d590d11e3e181be6014ead24f1132dd6cf5",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 13,
  "request_sha256": "b255d84b88072286b02fff840146a6e8202bb0466348e13176e3ed2fccf2058e",
  "round": 0,
  "signer": "j5qxkv.practice.antibody.testnet",
  "started_at": 1794184952
}

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

Check it yourself

tx 8WgdjVrY3h… · NEAR archival RPC

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

outlayer-verify tx 8WgdjVrY3hNzcLYtC8ZmodJKuFmxVbT2hxZEG4nmHe5d

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

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 181

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