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

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

Run · verification · program 16

Run 227

The enclave's verification of commit 106'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) · lowa841faaba0c4…, tag of slot 0: a841faaba0c424b249007c89a50fca0b4882825cde511c656ef0ccd415b59eea

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

2de3fccd6a6b89d4…

Request sha256

41f69380e042ff0c…

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

Output sha256

6c6ef7584454165f…

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 10:05:34 UTCDtKMkJzn…

Answered

2026-11-09 10:05:50 UTC16 s after it was requestedDtKMkJzn…

Commit

Commit 106

Program

Program 16round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

judge-2-p16.practice.antibody.testnet our check of a fresh practice program

Violationvault keeps its ether · low

receipt 2de3fccd6a6b…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.0001 wNEAR bond, by our check of a fresh practice program (judge-2-p16.practice.antibody.testnet).
AWNYoCuY…, NEAR transaction: AWNYoCuYXZny1JoZppDyUew4YLQwyNpJchZTWWawnpA8, opens an explorer in a new tab2026-11-0910:05:32 UTC · block 276,905,708
+2.5 s after the commit's block
Revealed · run 227 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 41f69380e042…, request sha256: 41f69380e042ff0c173c04b620a474095b8a0fa9878ec90c63c44bf8f6fa8251). 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 2de3fccd6a6b…, receipt sha256: 2de3fccd6a6b89d4ae44c6b04e007b24a6029a352ea625de5a91556780695be2. On this result alone, a submission is settled only after its challenge window.

Delivered in DtKMkJzn…, NEAR transaction: DtKMkJznncLGozDesZfsXSrtQfEghgVE1NsFTWSV4Dpa, opens an explorer in a new tab

Check it yourself

antibody status --run 227

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

{
  "commit": 106,
  "id": 227,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794218750,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "ef1ff36a21a74160d35f0a40d8024171c5043d0f7a87d0a4c4791e0457727936a6f613ed0bcf409097fcebbfb5a59e4aafb62682ede328238fd756c4"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "a841faaba0c424b249007c89a50fca0b4882825cde511c656ef0ccd415b59eea"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "2de3fccd6a6b89d4ae44c6b04e007b24a6029a352ea625de5a91556780695be2"
      },
      "output_sha256": "6c6ef7584454165fc07cdcbbd5a2b9a58c723c110af7aa94203882e897b36385",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 16,
  "request_sha256": "41f69380e042ff0c173c04b620a474095b8a0fa9878ec90c63c44bf8f6fa8251",
  "round": 0,
  "signer": "judge-2-p16.practice.antibody.testnet",
  "started_at": 1794218734
}

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

Check it yourself

tx DtKMkJznnc… · NEAR archival RPC

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

outlayer-verify tx DtKMkJznncLGozDesZfsXSrtQfEghgVE1NsFTWSV4Dpa

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

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 227

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