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

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

Run · verification · program 13

Run 178

The enclave's verification of commit 78'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) · lowd54485186613…, tag of slot 0: d544851866135513fbfe5d7c351963a877e4f42a65197ed53accc08e5bd9a032

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

715107ecbae62782…

Request sha256

668a03fabe9ec11d…

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

Output sha256

291dc9f34e078e1b…

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:41:22 UTCD37cxkH1…

Answered

2026-11-09 00:41:38 UTC16 s after it was requestedD37cxkH1…

Commit

Commit 78

Program

Program 13round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

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

Violationvault keeps its ether · low

receipt 715107ecbae6…

Timeline

Every step is a NEAR transaction, timed by block from commit 78'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 (j7qzvk.practice.antibody.testnet).
AXoemDi2…, NEAR transaction: AXoemDi2LMMmtcNHRnZFKsLkAPJX5MEHUhL3ce35NE9B, opens an explorer in a new tab2026-11-0900:41:17 UTC · block 276,849,585
+4.9 s after the commit's block
Revealed · run 178 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 668a03fabe9e…, request sha256: 668a03fabe9ec11d34fa4498149c9dfd9eed0345edf6060fc53ad2011020b386). 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 715107ecbae6…, receipt sha256: 715107ecbae627828523db28eb24d0511bf559c28da4ae1984b8507398a1d6fb. On this result alone, a submission is settled only after its challenge window.

Delivered in D37cxkH1…, NEAR transaction: D37cxkH1ZXDMHcjqDrRyRG6mG1G4gUZVXCC8Rj6BRKSa, opens an explorer in a new tab

Check it yourself

antibody status --run 178

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

{
  "commit": 78,
  "id": 178,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794184898,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "b7788fa5bcf8cf0ef8a3713aeb9c5ebe817077141bba6a15b999880df25b3343129b55616a2a6237f10072c3da255a899e6117d6c389b82a33c0f8fe"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "d544851866135513fbfe5d7c351963a877e4f42a65197ed53accc08e5bd9a032"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "715107ecbae627828523db28eb24d0511bf559c28da4ae1984b8507398a1d6fb"
      },
      "output_sha256": "291dc9f34e078e1b9c0701fd26e56bfa45593fbe46811bcf20b3cf1306332cd9",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 13,
  "request_sha256": "668a03fabe9ec11d34fa4498149c9dfd9eed0345edf6060fc53ad2011020b386",
  "round": 0,
  "signer": "j7qzvk.practice.antibody.testnet",
  "started_at": 1794184882
}

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

Check it yourself

tx D37cxkH1ZX… · NEAR archival RPC

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

outlayer-verify tx D37cxkH1ZXDMHcjqDrRyRG6mG1G4gUZVXCC8Rj6BRKSa

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

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 178

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