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

Run 64 · verification · Invalid proof · Attested on NEAR · Antibody

Run · verification · program 6

Run 64

The enclave's verification of commit 30's sealed proof: Invalid proof.

InvalidPoCAttested 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: InvalidPoC2 txs > cap 1
Keys: none: no rule broke
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: e1ce2d0027aa688b…, receipt sha256: e1ce2d0027aa688b0ec6ed4a23e03d4b25c26b4a7be1886466541161103b7d71
Request sha256: 009a553c0b4ea51f…, request sha256: 009a553c0b4ea51fad90c5e121070b2beeb2ecc4cef29fc8e3c458c16ed1a381
The SHA-256 of the input near-antibody sent the enclave: its result and its attestation bind to the same bytes.
Output sha256: 953c8aaa76095db3…, output sha256: 953c8aaa76095db342664346cb06427534214cf23150e3d73c9727abd85ae4cf
The SHA-256 of the facts near-antibody received: the TDX quote binds it.
Mode extras: none
Started: 2026-11-07 18:09:09 UTCHxQbudLZ…, NEAR transaction: HxQbudLZC9Z1zSEABo2zWvYAEttjhfmttpErouHsqNbR, opens an explorer in a new tab
Answered: 2026-11-07 18:09:34 UTC25 s after it was requestedHxQbudLZ…, NEAR transaction: HxQbudLZC9Z1zSEABo2zWvYAEttjhfmttpErouHsqNbR, opens an explorer in a new tab
Commit: Commit 30
Program: Program 6round 0
Paid for by: practice.antibody.testnet, account: practice.antibody.testnet the practice vending contract
Signed by: byo-invalid.practice.antibody.testnet, account: byo-invalid.practice.antibody.testnet our bring-your-own-proof check

InvalidPoCno rule broken

receipt e1ce2d0027aa…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.0001 wNEAR bond, by our bring-your-own-proof check (byo-invalid.practice.antibody.testnet).
DRmY7zqv…, NEAR transaction: DRmY7zqvyaRCaZ9Nayx6t6SgZV4MQeDfrohgBbwQUJC2, opens an explorer in a new tab2026-11-0718:09:06 UTC · block 276,665,827
+2.3 s after the commit's block
Revealed · run 64 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 009a553c0b4e…, request sha256: 009a553c0b4ea51fad90c5e121070b2beeb2ecc4cef29fc8e3c458c16ed1a381). 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: Invalid proof, receipt e1ce2d0027aa…, receipt sha256: e1ce2d0027aa688b0ec6ed4a23e03d4b25c26b4a7be1886466541161103b7d71. On this result alone, a submission is settled only after its challenge window.

Delivered in HxQbudLZ…, NEAR transaction: HxQbudLZC9Z1zSEABo2zWvYAEttjhfmttpErouHsqNbR, opens an explorer in a new tab

Check it yourself

antibody status --run 64

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

{
  "commit": 30,
  "id": 64,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794074974,
      "facts": {
        "extra": "None",
        "impact_usd_micro": "0",
        "keys": [],
        "kind": "InvalidPoC",
        "protected_harm_usd_micro": "0",
        "reason": "2 txs > cap 1",
        "receipt_sha256": "e1ce2d0027aa688b0ec6ed4a23e03d4b25c26b4a7be1886466541161103b7d71"
      },
      "output_sha256": "953c8aaa76095db342664346cb06427534214cf23150e3d73c9727abd85ae4cf",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 6,
  "request_sha256": "009a553c0b4ea51fad90c5e121070b2beeb2ecc4cef29fc8e3c458c16ed1a381",
  "round": 0,
  "signer": "byo-invalid.practice.antibody.testnet",
  "started_at": 1794074949
}

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

Check it yourself

tx HxQbudLZC9… · NEAR archival RPC

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

outlayer-verify tx HxQbudLZC9Z1zSEABo2zWvYAEttjhfmttpErouHsqNbR

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

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 64

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