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

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

Run · verification · program 14

Run 208

The enclave's verification of commit 98'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) · lowa0b98404781f…, tag of slot 0: a0b98404781f6774c498ba8a64b935ce732dd5dc9d89fe0651748aff7a1517b9

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

e963bba596c9bdd0…

Request sha256

717d616beac145ea…

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

Output sha256

37be157141d95dce…

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:48:20 UTCBbGj24Vr…

Answered

2026-11-09 01:48:34 UTC14 s after it was requestedBbGj24Vr…

Commit

Commit 98

Program

Program 14round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

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

Violationvault keeps its ether · low

receipt e963bba596c9…

Timeline

Every step is a NEAR transaction, timed by block from commit 98'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 (j8snqk.practice.antibody.testnet).
EQbGCTrg…, NEAR transaction: EQbGCTrgkEaHjvuApsmP5jyxrQazyTEo57JrEEzKg2pA, opens an explorer in a new tab2026-11-0901:48:17 UTC · block 276,856,265
+3.0 s after the commit's block
Revealed · run 208 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 717d616beac1…, request sha256: 717d616beac145eae5bba959fd4e190978f9d7542891ecd250179eb7023749d2). 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 e963bba596c9…, receipt sha256: e963bba596c9bdd0871456e24a0152217ada6b4c1dcb22075117ce00872b701f. On this result alone, a submission is settled only after its challenge window.

Delivered in BbGj24Vr…, NEAR transaction: BbGj24VrvMcSMvFryRi3NwCs5HrWapcnjHhrEeBJkk73, opens an explorer in a new tab

Check it yourself

antibody status --run 208

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

{
  "commit": 98,
  "id": 208,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794188914,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "a86dad3780265f59c674ef974278ce5f577cf3f15202b3773b9e144a82b347d2b9d44cdbc5964781ea9552163249ce96adbde50c3756b0ad6808468b"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "a0b98404781f6774c498ba8a64b935ce732dd5dc9d89fe0651748aff7a1517b9"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "e963bba596c9bdd0871456e24a0152217ada6b4c1dcb22075117ce00872b701f"
      },
      "output_sha256": "37be157141d95dce6b6ee47319e21d35d1a6f5398c8f8ac1e5b53fe8c2a416e9",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 14,
  "request_sha256": "717d616beac145eae5bba959fd4e190978f9d7542891ecd250179eb7023749d2",
  "round": 0,
  "signer": "j8snqk.practice.antibody.testnet",
  "started_at": 1794188900
}

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

Check it yourself

tx BbGj24VrvM… · NEAR archival RPC

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

outlayer-verify tx BbGj24VrvMcSMvFryRi3NwCs5HrWapcnjHhrEeBJkk73

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

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 208

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