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

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

Run · verification · program 10

Run 85

The enclave's verification of commit 47'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) · low3dc9b3fbc56f…, tag of slot 0: 3dc9b3fbc56fb5d89b1fb1a957760631e1381b9cb66c93e3621521d020fd109b

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

0e69471b5718f31b…

Request sha256

d9531876a149c3f0…

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

Output sha256

ac3cc5cd865e236e…

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-08 09:18:32 UTCJ1PMxU2X…

Answered

2026-11-08 09:18:48 UTC16 s after it was requestedJ1PMxU2X…

Commit

Commit 47

Program

Program 10round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

m11080904-09.practice.antibody.testnet a measured agent run (docs/agent-runs.md)

Violationvault keeps its ether · low

receipt 0e69471b5718…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.0001 wNEAR bond, by a measured agent run (docs/agent-runs.md) (m11080904-09.practice.antibody.testnet).
99g4LarF…, NEAR transaction: 99g4LarFPTRiZm2ya2k3KvzoxCvNFZctGEVnZ9AHGT3u, opens an explorer in a new tab2026-11-0809:18:30 UTC · block 276,756,375
+2.4 s after the commit's block
Revealed · run 85 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 d9531876a149…, request sha256: d9531876a149c3f0fbd0420e22890ef4377f6afd7d677764217c1f72bda0275f). 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 0e69471b5718…, receipt sha256: 0e69471b5718f31b26d84edfa689fdf1a258a8fc99afe8ad62253088b8f4cf00. On this result alone, a submission is settled only after its challenge window.

Delivered in J1PMxU2X…, NEAR transaction: J1PMxU2XPLCKntK3Fyb7qzNxm6ypDPKHqYbS5w97jRtk, opens an explorer in a new tab

Check it yourself

antibody status --run 85

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

{
  "commit": 47,
  "id": 85,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794129528,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "12bdc31cd02f103731da6c7203e27b9b40c024acedb1c232aa000c42516e1ab722576b51dfcb1e34b340ee77598a96d79f174433515566138cc8aa2f"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "3dc9b3fbc56fb5d89b1fb1a957760631e1381b9cb66c93e3621521d020fd109b"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "0e69471b5718f31b26d84edfa689fdf1a258a8fc99afe8ad62253088b8f4cf00"
      },
      "output_sha256": "ac3cc5cd865e236ea7a7f4dff81bdcaa63e6d87d6d5a0c5e8d00551fc8ac2aff",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 10,
  "request_sha256": "d9531876a149c3f0fbd0420e22890ef4377f6afd7d677764217c1f72bda0275f",
  "round": 0,
  "signer": "m11080904-09.practice.antibody.testnet",
  "started_at": 1794129512
}

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

Check it yourself

tx J1PMxU2XPL… · NEAR archival RPC

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

outlayer-verify tx J1PMxU2XPLCKntK3Fyb7qzNxm6ypDPKHqYbS5w97jRtk

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

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 85

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