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

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

Run · verification · program 14

Run 206

The enclave's verification of commit 96'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) · lowcc8dfdd9d152…, tag of slot 0: cc8dfdd9d152505937dabc824d0bde428c720a96a72192a59c67741ffb5ed4c8

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

a722e9763b10b081…

Request sha256

854af97c5c68a08c…

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

Output sha256

d8a61081de895d7d…

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:47:31 UTCGeLnFbub…

Answered

2026-11-09 01:47:45 UTC14 s after it was requestedGeLnFbub…

Commit

Commit 96

Program

Program 14round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

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

Violationvault keeps its ether · low

receipt a722e9763b10…

Timeline

Every step is a NEAR transaction, timed by block from commit 96'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 (j7bkmr.practice.antibody.testnet).
EW7dvNRL…, NEAR transaction: EW7dvNRLyw2oi1uo5e5MHNS4mfXVZBuuhbipFwTsooJh, opens an explorer in a new tab2026-11-0901:47:27 UTC · block 276,856,183
+3.5 s after the commit's block
Revealed · run 206 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 854af97c5c68…, request sha256: 854af97c5c68a08c50161e2580cd49329e7ddf4006904838ee57370e4c4d0306). 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 a722e9763b10…, receipt sha256: a722e9763b10b081f3428ff5fb303a5fc33e1977a53898537e45f6c54c5aeb41. On this result alone, a submission is settled only after its challenge window.

Delivered in GeLnFbub…, NEAR transaction: GeLnFbubxEbZhizMgi4JCTQRzToMzsaPUmYAgeaSynU5, opens an explorer in a new tab

Check it yourself

antibody status --run 206

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

{
  "commit": 96,
  "id": 206,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794188865,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "65651833b0847a93de43064cfc1532924ec5116f923dcf1917056e50af264fdf56b73b8e37eef19430d59f248b9f6863cbb58a74f5b2d95eb0d57041"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "cc8dfdd9d152505937dabc824d0bde428c720a96a72192a59c67741ffb5ed4c8"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "a722e9763b10b081f3428ff5fb303a5fc33e1977a53898537e45f6c54c5aeb41"
      },
      "output_sha256": "d8a61081de895d7db67e5b49005ec13ca9460cce4789255a6893c56178773d1f",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 14,
  "request_sha256": "854af97c5c68a08c50161e2580cd49329e7ddf4006904838ee57370e4c4d0306",
  "round": 0,
  "signer": "j7bkmr.practice.antibody.testnet",
  "started_at": 1794188851
}

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

Check it yourself

tx GeLnFbubxE… · NEAR archival RPC

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

outlayer-verify tx GeLnFbubxEbZhizMgi4JCTQRzToMzsaPUmYAgeaSynU5

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

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 206

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