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

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

Run · verification · program 14

Run 195

The enclave's verification of commit 90'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) · low7e5310d05e0e…, tag of slot 0: 7e5310d05e0ea851ec72744aa506c6df93825d8713b379841cd9adbc2f7db290

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

146010480f4dfa80…

Request sha256

37cefed39d4fd9a1…

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

Output sha256

b7ab034a73c91533…

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:39:19 UTC8ancNhMn…

Answered

2026-11-09 01:39:33 UTC14 s after it was requested8ancNhMn…

Commit

Commit 90

Program

Program 14round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

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

Violationvault keeps its ether · low

receipt 146010480f4d…

Timeline

Every step is a NEAR transaction, timed by block from commit 90'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 (j1qzkw.practice.antibody.testnet).
JCbGEDox…, NEAR transaction: JCbGEDoxNC4WhzWuS8M5bHccUCpFBTuibX4mEVJirw5e, opens an explorer in a new tab2026-11-0901:39:15 UTC · block 276,855,359
+4.4 s after the commit's block
Revealed · run 195 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 37cefed39d4f…, request sha256: 37cefed39d4fd9a184177caa4fc86f29702de1101be4d4d1f42f152a457a186c). 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 146010480f4d…, receipt sha256: 146010480f4dfa800cb4f87d1d7f070bd378e6b0aeee3fff9e34d29a0c83a563. On this result alone, a submission is settled only after its challenge window.

Delivered in 8ancNhMn…, NEAR transaction: 8ancNhMnWAfsgykUiQJvzd9Wc4TrrsfNaLZ3VqwmqxnQ, opens an explorer in a new tab

Check it yourself

antibody status --run 195

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

{
  "commit": 90,
  "id": 195,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794188373,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "0a2e3fdbdb238a058734d19879582cf19498f2a3e225f12a61b8cf19fbc55a115231a589acd25e7b82ff9a50f6f2497aef7d5c75b635c9c524b9f7a4"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "7e5310d05e0ea851ec72744aa506c6df93825d8713b379841cd9adbc2f7db290"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "146010480f4dfa800cb4f87d1d7f070bd378e6b0aeee3fff9e34d29a0c83a563"
      },
      "output_sha256": "b7ab034a73c91533804d5d230d3235f46fc83238815b84bfd5fbda2e310502ea",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 14,
  "request_sha256": "37cefed39d4fd9a184177caa4fc86f29702de1101be4d4d1f42f152a457a186c",
  "round": 0,
  "signer": "j1qzkw.practice.antibody.testnet",
  "started_at": 1794188359
}

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

Check it yourself

tx 8ancNhMnWA… · NEAR archival RPC

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

outlayer-verify tx 8ancNhMnWAfsgykUiQJvzd9Wc4TrrsfNaLZ3VqwmqxnQ

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

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 195

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