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

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

Run · verification · program 14

Run 194

The enclave's verification of commit 89'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) · low274ab866afd8…, tag of slot 0: 274ab866afd8fb689cb7efed9d867b84fe2eeccde2745aa0d363ebf32f72959e

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

9e1688da0566ad97…

Request sha256

70d078607689bbe4…

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

Output sha256

aaa8b5ba5b3ff3dc…

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:15 UTC2rfpKeuM…

Answered

2026-11-09 01:39:34 UTC19 s after it was requested2rfpKeuM…

Commit

Commit 89

Program

Program 14round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

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

Violationvault keeps its ether · low

receipt 9e1688da0566…

Timeline

Every step is a NEAR transaction, timed by block from commit 89'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 (j2qzvn.practice.antibody.testnet).
5PiDSbzV…, NEAR transaction: 5PiDSbzVgG3bVEnS5VLVtV3PeXb125tQdYE7HV9rp8Dp, opens an explorer in a new tab2026-11-0901:39:13 UTC · block 276,855,356
+2.4 s after the commit's block
Revealed · run 194 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 70d078607689…, request sha256: 70d078607689bbe4ed342af0185d8b67e746cd18a48c4db90866226e7ff8e04c). 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 9e1688da0566…, receipt sha256: 9e1688da0566ad97c3f595b7ca426398ca0656e4689d375c20861b2bf2e31883. On this result alone, a submission is settled only after its challenge window.

Delivered in 2rfpKeuM…, NEAR transaction: 2rfpKeuMiDWPc3aEwXeKcMiWgpaFEMqYgTiENDkD2scA, opens an explorer in a new tab

Check it yourself

antibody status --run 194

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

{
  "commit": 89,
  "id": 194,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794188374,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "1bedc91146dba5d43182c13499d83bb049f686aac6edd18ee988840247756c588b8a7ebd8d4bb552ae7c7fef7f9714aff69bca7e91d6e01cccf8e15b"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "274ab866afd8fb689cb7efed9d867b84fe2eeccde2745aa0d363ebf32f72959e"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "9e1688da0566ad97c3f595b7ca426398ca0656e4689d375c20861b2bf2e31883"
      },
      "output_sha256": "aaa8b5ba5b3ff3dce9233826815e4973f6e46b152f593b1402ca857c9ab92723",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 14,
  "request_sha256": "70d078607689bbe4ed342af0185d8b67e746cd18a48c4db90866226e7ff8e04c",
  "round": 0,
  "signer": "j2qzvn.practice.antibody.testnet",
  "started_at": 1794188355
}

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

Check it yourself

tx 2rfpKeuMiD… · NEAR archival RPC

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

outlayer-verify tx 2rfpKeuMiDWPc3aEwXeKcMiWgpaFEMqYgTiENDkD2scA

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

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 194

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