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

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

Run · verification · program 2

Run 27

The enclave's verification of commit 11'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) · low07fdd94722c2…, tag of slot 0: 07fdd94722c2a4d685427074100718d9e20a4de25866f0c06fc53243909e9650

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

aca6f1352b8e6ef6…

Request sha256

39e3b6b813873d50…

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

Output sha256

92a05e9eab829e25…

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-03 14:20:43 UTCDHdtvdPZ…

Answered

2026-11-03 14:20:57 UTC14 s after it was requestedDHdtvdPZ…

Commit

Commit 11

Program

Program 2round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

check-1.practice.antibody.testnet an earlier run's practice try

Violationvault keeps its ether · low

receipt aca6f1352b8e…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.0001 wNEAR bond, by an earlier run's practice try (check-1.practice.antibody.testnet).
EsYr923D…, NEAR transaction: EsYr923DuaQhAykgmfXwW63rACs8qVybgCkokYQ1Au8o, opens an explorer in a new tab2026-11-0314:20:40 UTC · block 276,060,508
+2.5 s after the commit's block
Revealed · run 27 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 39e3b6b81387…, request sha256: 39e3b6b813873d50e3698b04aee22d4fdc0c70cca5d9985cff6c5b09fd7d6372). 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 aca6f1352b8e…, receipt sha256: aca6f1352b8e6ef6cca817d9d8740d494746572fb32272fb079bfeed9641440f. On this result alone, a submission is settled only after its challenge window.

Delivered in DHdtvdPZ…, NEAR transaction: DHdtvdPZjUEbm9e7cb8YzVrjhAXJWQkHhoQNvPswNArn, opens an explorer in a new tab

Check it yourself

antibody status --run 27

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

{
  "commit": 11,
  "id": 27,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1793715657,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "65f409c290acc44b9ac8d9f56cfb8566abca633c609a4fbae48907d7ff16ea969b8d2a6617c91e3eb94ad68383bb5f75aea66611f0b39ebf37ce6135"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "07fdd94722c2a4d685427074100718d9e20a4de25866f0c06fc53243909e9650"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "aca6f1352b8e6ef6cca817d9d8740d494746572fb32272fb079bfeed9641440f"
      },
      "output_sha256": "92a05e9eab829e25162a24c123eb2588cad606510a6214383c63ba28a878d79d",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 2,
  "request_sha256": "39e3b6b813873d50e3698b04aee22d4fdc0c70cca5d9985cff6c5b09fd7d6372",
  "round": 0,
  "signer": "check-1.practice.antibody.testnet",
  "started_at": 1793715643
}

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

Check it yourself

tx DHdtvdPZjU… · NEAR archival RPC

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

outlayer-verify tx DHdtvdPZjUEbm9e7cb8YzVrjhAXJWQkHhoQNvPswNArn

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

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 27

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