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

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

Run · verification · program 13

Run 179

The enclave's verification of commit 79'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) · low1c4489f727ea…, tag of slot 0: 1c4489f727ea0e851d7c5f3ff1c4054966e5649ae4da6dde6315a8ccc588ad9f

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

a1e72e3415cef153…

Request sha256

8fe55f78758ddc4e…

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

Output sha256

f51f8ee5f7ceb307…

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:32 UTC7LBJEKAk…

Answered

2026-11-09 00:41:47 UTC15 s after it was requested7LBJEKAk…

Commit

Commit 79

Program

Program 13round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

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

Violationvault keeps its ether · low

receipt a1e72e3415ce…

Timeline

Every step is a NEAR transaction, timed by block from commit 79'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 (j6kqzv.practice.antibody.testnet).
8zYqvAze…, NEAR transaction: 8zYqvAzehn24PADRGjdi8iJsFzppqzrLr979QJWW16aM, opens an explorer in a new tab2026-11-0900:41:29 UTC · block 276,849,604
+2.5 s after the commit's block
Revealed · run 179 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 8fe55f78758d…, request sha256: 8fe55f78758ddc4ec8c8820d4963825edfe7c0cf02f4e5d04aa9bfb2afe67ce6). 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 a1e72e3415ce…, receipt sha256: a1e72e3415cef153c2cd4e86c206fd024a0cb2b9dcf2241e78b2fa2473353c63. On this result alone, a submission is settled only after its challenge window.

Delivered in 7LBJEKAk…, NEAR transaction: 7LBJEKAkH9azQDxSFnJ5LvJnuuc1uTRGHSvxwYqDwfA, opens an explorer in a new tab

Check it yourself

antibody status --run 179

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

{
  "commit": 79,
  "id": 179,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794184907,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "9c1b29dfec941ed8b6cb13119c91fd940f00239ab517e029792f96c6190c3c036f84d7ae47985a60bd1f902031efdbbb274e0ab416a2933f27a43904"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "1c4489f727ea0e851d7c5f3ff1c4054966e5649ae4da6dde6315a8ccc588ad9f"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "a1e72e3415cef153c2cd4e86c206fd024a0cb2b9dcf2241e78b2fa2473353c63"
      },
      "output_sha256": "f51f8ee5f7ceb307b512cc1d2c5801874ad027a6221d91a75059243111dc8abb",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 13,
  "request_sha256": "8fe55f78758ddc4ec8c8820d4963825edfe7c0cf02f4e5d04aa9bfb2afe67ce6",
  "round": 0,
  "signer": "j6kqzv.practice.antibody.testnet",
  "started_at": 1794184892
}

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

Check it yourself

tx 7LBJEKAkH9… · NEAR archival RPC

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

outlayer-verify tx 7LBJEKAkH9azQDxSFnJ5LvJnuuc1uTRGHSvxwYqDwfA

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

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 179

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