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

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

Run · verification · program 10

Run 89

The enclave's verification of commit 51'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) · lowfc75e43995c7…, tag of slot 0: fc75e43995c70c12e98fa8d4f96c7dc68ed68df88c2b122522bc5adf1ab96965

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

82a9207b4e05af2a…

Request sha256

f123badd6303a606…

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

Output sha256

b381f49735ebd964…

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:25:00 UTC7uQG3gMh…

Answered

2026-11-08 09:25:15 UTC15 s after it was requested7uQG3gMh…

Commit

Commit 51

Program

Program 10round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

m11080919-03.practice.antibody.testnet a measured agent run (docs/agent-runs.md)

Violationvault keeps its ether · low

receipt 82a9207b4e05…

Timeline

Every step is a NEAR transaction, timed by block from commit 51'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) (m11080919-03.practice.antibody.testnet).
3NWDzrBM…, NEAR transaction: 3NWDzrBMUvaEzSknjbgRu4SSFFAT3BWjZUseoDhRqgh9, opens an explorer in a new tab2026-11-0809:24:58 UTC · block 276,757,020
+2.3 s after the commit's block
Revealed · run 89 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 f123badd6303…, request sha256: f123badd6303a6065d210d5559212bd9b0255c4181b61c1e952c8134e046c340). 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 82a9207b4e05…, receipt sha256: 82a9207b4e05af2a0f1a4ab41b935fe082aff7118e8ef6c17b8df93a6d1f667d. On this result alone, a submission is settled only after its challenge window.

Delivered in 7uQG3gMh…, NEAR transaction: 7uQG3gMhFv31Y8dfjUDis3b99fN5Jow9FrwF746gTeCx, opens an explorer in a new tab

Check it yourself

antibody status --run 89

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

{
  "commit": 51,
  "id": 89,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794129915,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "5a17522a6535ede6542687969b3d519dceed8c17badf26e18a1aa43be15c82c5a1fda0ec55fdf18ffe64371b5d825a3c56802201e19109708cafcfd2"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "fc75e43995c70c12e98fa8d4f96c7dc68ed68df88c2b122522bc5adf1ab96965"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "82a9207b4e05af2a0f1a4ab41b935fe082aff7118e8ef6c17b8df93a6d1f667d"
      },
      "output_sha256": "b381f49735ebd964b13f9dc2db2675675c10c31411a4e100d798d16cc89030e9",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 10,
  "request_sha256": "f123badd6303a6065d210d5559212bd9b0255c4181b61c1e952c8134e046c340",
  "round": 0,
  "signer": "m11080919-03.practice.antibody.testnet",
  "started_at": 1794129900
}

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

Check it yourself

tx 7uQG3gMhFv… · NEAR archival RPC

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

outlayer-verify tx 7uQG3gMhFv31Y8dfjUDis3b99fN5Jow9FrwF746gTeCx

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

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 89

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