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

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

Run · verification · program 6

Run 59

The enclave's verification of commit 25'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) · low3819758f5bf9…, tag of slot 0: 3819758f5bf9959a08ac811a8848d42799527427ce06f861e61e8c225c68e906

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

d313eef0b3909550…

Request sha256

7cba6e8ba9e2490a…

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

Output sha256

18f76bee17b7557e…

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-07 13:06:12 UTC3N9A4NS3…

Answered

2026-11-07 13:06:26 UTC14 s after it was requested3N9A4NS3…

Commit

Commit 25

Program

Program 6round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

site-check.practice.antibody.testnet our check of the deployed site

Violationvault keeps its ether · low

receipt d313eef0b390…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.0001 wNEAR bond, by our check of the deployed site (site-check.practice.antibody.testnet).
AgDZg86W…, NEAR transaction: AgDZg86WwRhmrvSu7fn8FRqZ7jBTpbjyqzEL4rUpBQR, opens an explorer in a new tab2026-11-0713:06:09 UTC · block 276,634,849
+2.5 s after the commit's block
Revealed · run 59 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 7cba6e8ba9e2…, request sha256: 7cba6e8ba9e2490ae44fe92298fd171b507dbdee1aa43393ea5742e68d38a4b5). 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 d313eef0b390…, receipt sha256: d313eef0b3909550f4f6c53784dbfcb9249ec4773bcb33946dd435411c4d364b. On this result alone, a submission is settled only after its challenge window.

Delivered in 3N9A4NS3…, NEAR transaction: 3N9A4NS3RYJktiriYhcXx5NSfkeE5tuURxbAWUkNd7LR, opens an explorer in a new tab

Check it yourself

antibody status --run 59

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

{
  "commit": 25,
  "id": 59,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794056786,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "c7dee9936cc0c9eb9a2b71bbb8cde9a6f64aa270d3514b0723f3295ccec234ab891c094dd9339a196876548cab2919187977b76ce45e10996f67202c"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "3819758f5bf9959a08ac811a8848d42799527427ce06f861e61e8c225c68e906"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "d313eef0b3909550f4f6c53784dbfcb9249ec4773bcb33946dd435411c4d364b"
      },
      "output_sha256": "18f76bee17b7557ea9ff948b674b3fba8be297f4f313cd9e2d49d99736230643",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 6,
  "request_sha256": "7cba6e8ba9e2490ae44fe92298fd171b507dbdee1aa43393ea5742e68d38a4b5",
  "round": 0,
  "signer": "site-check.practice.antibody.testnet",
  "started_at": 1794056772
}

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

Check it yourself

tx 3N9A4NS3RY… · NEAR archival RPC

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

outlayer-verify tx 3N9A4NS3RYJktiriYhcXx5NSfkeE5tuURxbAWUkNd7LR

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

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 59

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