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

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

Run · verification · program 10

Run 81

The enclave's verification of commit 43'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) · low46b4382c82f6…, tag of slot 0: 46b4382c82f61db7c2e900a59a86c514d02ad6bebfc6714103539d898dcff7d9

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

5bc1a3122fb00995…

Request sha256

53b130b9fe092e48…

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

Output sha256

c204030626ff892d…

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:12:15 UTCDy3YmsQC…

Answered

2026-11-08 09:12:29 UTC14 s after it was requestedDy3YmsQC…

Commit

Commit 43

Program

Program 10round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

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

Violationvault keeps its ether · low

receipt 5bc1a3122fb0…

Timeline

Every step is a NEAR transaction, timed by block from commit 43'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-05.practice.antibody.testnet).
5TLe5y3d…, NEAR transaction: 5TLe5y3d9BngVz4xKM59aFoPyCciGB8daYAoTbHCTpuG, opens an explorer in a new tab2026-11-0809:12:12 UTC · block 276,755,752
+2.5 s after the commit's block
Revealed · run 81 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 53b130b9fe09…, request sha256: 53b130b9fe092e48c1542781b94959825abd7b8e227ca01383c9d6cdf322f8d5). 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 5bc1a3122fb0…, receipt sha256: 5bc1a3122fb009950ee4f98c14798520b004921678f9d6bb29971d835a8beb30. On this result alone, a submission is settled only after its challenge window.

Delivered in Dy3YmsQC…, NEAR transaction: Dy3YmsQCPJUMcAfSkqCA8r6wTTEy5RiR4djMcc5UZTRq, opens an explorer in a new tab

Check it yourself

antibody status --run 81

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

{
  "commit": 43,
  "id": 81,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794129149,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "a02e5c1033de9fa7722535611a1ad5d3966adbbd0bbb3f29b7d746f8108d758ac0898f9e3cec16c81e5d3bf1ff37697da29953233a1d08f46a274094"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "46b4382c82f61db7c2e900a59a86c514d02ad6bebfc6714103539d898dcff7d9"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "5bc1a3122fb009950ee4f98c14798520b004921678f9d6bb29971d835a8beb30"
      },
      "output_sha256": "c204030626ff892dcae33948f6fdf8fab9a82c6c97a41d40fb4688c7b9f361d8",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 10,
  "request_sha256": "53b130b9fe092e48c1542781b94959825abd7b8e227ca01383c9d6cdf322f8d5",
  "round": 0,
  "signer": "m11080904-05.practice.antibody.testnet",
  "started_at": 1794129135
}

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

Check it yourself

tx Dy3YmsQCPJ… · NEAR archival RPC

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

outlayer-verify tx Dy3YmsQCPJUMcAfSkqCA8r6wTTEy5RiR4djMcc5UZTRq

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

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 81

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