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

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

Run · verification · program 6

Run 57

The enclave's verification of commit 23'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) · low9990e991d8bc…, tag of slot 0: 9990e991d8bcee767113d2bfb18a2100da8db6f5f1be40db08339fb7ce91453c

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

4b07c8f7a21da617…

Request sha256

0c5980f43a8b1335…

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

Output sha256

909d8c7bc1abaaae…

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-06 13:03:27 UTC6T82L9ZE…

Answered

2026-11-06 13:03:42 UTC15 s after it was requested6T82L9ZE…

Commit

Commit 23

Program

Program 6round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

pcs-rehearsal.practice.antibody.testnet our rehearsal

Violationvault keeps its ether · low

receipt 4b07c8f7a21d…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.0001 wNEAR bond, by our rehearsal (pcs-rehearsal.practice.antibody.testnet).
2hGsGMWE…, NEAR transaction: 2hGsGMWEkjoV51YFECVgFdZPNuukt8coUJSfhgC7FJ8f, opens an explorer in a new tab2026-11-0613:03:25 UTC · block 276,490,216
+1.9 s after the commit's block
Revealed · run 57 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 0c5980f43a8b…, request sha256: 0c5980f43a8b1335bd60aead70dd51fd98d58e3b170291295494853d2754cc6f). 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 4b07c8f7a21d…, receipt sha256: 4b07c8f7a21da617246c877d2f2e64661ea00c01ad89fbc7e83a72ed29202530. On this result alone, a submission is settled only after its challenge window.

Delivered in 6T82L9ZE…, NEAR transaction: 6T82L9ZE8ALbTSJ5ntmJNwHtpaLuACbjqgfDYzKp8VJd, opens an explorer in a new tab

Check it yourself

antibody status --run 57

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

{
  "commit": 23,
  "id": 57,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1793970222,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "353f18dce295f1125222eab5c5ea952a386214595954b03ff2513b0a22714ae8103be271dfdba593ac95d83e2287205885d07c0d7c8c317d4aee78d5"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "9990e991d8bcee767113d2bfb18a2100da8db6f5f1be40db08339fb7ce91453c"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "4b07c8f7a21da617246c877d2f2e64661ea00c01ad89fbc7e83a72ed29202530"
      },
      "output_sha256": "909d8c7bc1abaaae1791228783a96fb0f99ebd88bb36c6ca1471f3b5092babd8",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 6,
  "request_sha256": "0c5980f43a8b1335bd60aead70dd51fd98d58e3b170291295494853d2754cc6f",
  "round": 0,
  "signer": "pcs-rehearsal.practice.antibody.testnet",
  "started_at": 1793970207
}

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

Check it yourself

tx 6T82L9ZE8A… · NEAR archival RPC

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

outlayer-verify tx 6T82L9ZE8ALbTSJ5ntmJNwHtpaLuACbjqgfDYzKp8VJd

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

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 57

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