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

Run 63 · verification · No violation · Attested on NEAR · Antibody

Run · verification · program 6

Run 63

The enclave's verification of commit 29's sealed proof: No violation.

No 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: No violation
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: 0c8e23c8c989b438…, receipt sha256: 0c8e23c8c989b438e2a32e202b7da312db5298e3c7d75c8ea21c7d6c41d6626f
Request sha256: 2f2aaefb17d7c00b…, request sha256: 2f2aaefb17d7c00b3227a2083e08e3d19c0fdce304d16341452f88bf8d205197
The SHA-256 of the input near-antibody sent the enclave: its result and its attestation bind to the same bytes.
Output sha256: 5938e5da89158c7c…, output sha256: 5938e5da89158c7c26ee27ae6561b3eb2e544adb95ca670e89881589b776add1
The SHA-256 of the facts near-antibody received: the TDX quote binds it.
Mode extras: none
Started: 2026-11-07 18:07:31 UTC332SYN2k…, NEAR transaction: 332SYN2kj9smg9ju9EZ25JSda1Ue7mT8C4b1EwDXAKyb, opens an explorer in a new tab
Answered: 2026-11-07 18:07:48 UTC17 s after it was requested332SYN2k…, NEAR transaction: 332SYN2kj9smg9ju9EZ25JSda1Ue7mT8C4b1EwDXAKyb, opens an explorer in a new tab
Commit: Commit 29
Program: Program 6round 0
Paid for by: practice.antibody.testnet, account: practice.antibody.testnet the practice vending contract
Signed by: byo-wrong.practice.antibody.testnet, account: byo-wrong.practice.antibody.testnet our bring-your-own-proof check

No violationno rule broken

receipt 0c8e23c8c989…

Timeline

Every step is a NEAR transaction, timed by block from commit 29'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-wrong.practice.antibody.testnet).
7wEBuvSE…, NEAR transaction: 7wEBuvSECgoZio8FRUbsb1A8aXYVm3KBNS8aHfcWEkLq, opens an explorer in a new tab2026-11-0718:07:29 UTC · block 276,665,666
+2.6 s after the commit's block
Revealed · run 63 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 2f2aaefb17d7…, request sha256: 2f2aaefb17d7c00b3227a2083e08e3d19c0fdce304d16341452f88bf8d205197). 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: No violation, receipt 0c8e23c8c989…, receipt sha256: 0c8e23c8c989b438e2a32e202b7da312db5298e3c7d75c8ea21c7d6c41d6626f. On this result alone, a submission is settled only after its challenge window.

Delivered in 332SYN2k…, NEAR transaction: 332SYN2kj9smg9ju9EZ25JSda1Ue7mT8C4b1EwDXAKyb, opens an explorer in a new tab

Check it yourself

antibody status --run 63

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

{
  "commit": 29,
  "id": 63,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794074868,
      "facts": {
        "extra": "None",
        "impact_usd_micro": "0",
        "keys": [],
        "kind": "NoViolation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "0c8e23c8c989b438e2a32e202b7da312db5298e3c7d75c8ea21c7d6c41d6626f"
      },
      "output_sha256": "5938e5da89158c7c26ee27ae6561b3eb2e544adb95ca670e89881589b776add1",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 6,
  "request_sha256": "2f2aaefb17d7c00b3227a2083e08e3d19c0fdce304d16341452f88bf8d205197",
  "round": 0,
  "signer": "byo-wrong.practice.antibody.testnet",
  "started_at": 1794074851
}

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

Check it yourself

tx 332SYN2kj9… · NEAR archival RPC

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

outlayer-verify tx 332SYN2kj9smg9ju9EZ25JSda1Ue7mT8C4b1EwDXAKyb

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

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 63

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