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

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

Run · verification · program 14

Run 197

The enclave's verification of commit 92'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: 70a5ef9a9930ee41…, receipt sha256: 70a5ef9a9930ee41587939a45835ba1c8e94f48381861a1344ecf03998786408
Request sha256: 14e518561b8e3a68…, request sha256: 14e518561b8e3a6880b3c89dd5b5291eec9df9a2bec9b0962c8e163b60749808
The SHA-256 of the input near-antibody sent the enclave: its result and its attestation bind to the same bytes.
Output sha256: 609382eada136a3c…, output sha256: 609382eada136a3cef34da91b56adb098d5bdc0e927219e195734924e66bde02
The SHA-256 of the facts near-antibody received: the TDX quote binds it.
Mode extras: none
Started: 2026-11-09 01:41:28 UTC6AW34cWt…, NEAR transaction: 6AW34cWtwWteDKtoG33hAw71SntCyPPRG9TBhApUsquK, opens an explorer in a new tab
Answered: 2026-11-09 01:41:41 UTC13 s after it was requested6AW34cWt…, NEAR transaction: 6AW34cWtwWteDKtoG33hAw71SntCyPPRG9TBhApUsquK, opens an explorer in a new tab
Commit: Commit 92
Program: Program 14round 0
Paid for by: practice.antibody.testnet, account: practice.antibody.testnet the practice vending contract
Signed by: j3hwpd.practice.antibody.testnet, account: j3hwpd.practice.antibody.testnet a visitor's practice try

No violationno rule broken

receipt 70a5ef9a9930…

Timeline

Every step is a NEAR transaction, timed by block from commit 92'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 (j3hwpd.practice.antibody.testnet).
GrV2NoPn…, NEAR transaction: GrV2NoPne2CYeGqaJsB8wKZesdbtwodMiLpskiF1fT7Z, opens an explorer in a new tab2026-11-0901:41:24 UTC · block 276,855,572
+4.3 s after the commit's block
Revealed · run 197 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 14e518561b8e…, request sha256: 14e518561b8e3a6880b3c89dd5b5291eec9df9a2bec9b0962c8e163b60749808). 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 70a5ef9a9930…, receipt sha256: 70a5ef9a9930ee41587939a45835ba1c8e94f48381861a1344ecf03998786408. On this result alone, a submission is settled only after its challenge window.

Delivered in 6AW34cWt…, NEAR transaction: 6AW34cWtwWteDKtoG33hAw71SntCyPPRG9TBhApUsquK, opens an explorer in a new tab

Check it yourself

antibody status --run 197

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

{
  "commit": 92,
  "id": 197,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794188501,
      "facts": {
        "extra": "None",
        "impact_usd_micro": "0",
        "keys": [],
        "kind": "NoViolation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "70a5ef9a9930ee41587939a45835ba1c8e94f48381861a1344ecf03998786408"
      },
      "output_sha256": "609382eada136a3cef34da91b56adb098d5bdc0e927219e195734924e66bde02",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 14,
  "request_sha256": "14e518561b8e3a6880b3c89dd5b5291eec9df9a2bec9b0962c8e163b60749808",
  "round": 0,
  "signer": "j3hwpd.practice.antibody.testnet",
  "started_at": 1794188488
}

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

Check it yourself

tx 6AW34cWtwW… · NEAR archival RPC

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

outlayer-verify tx 6AW34cWtwWteDKtoG33hAw71SntCyPPRG9TBhApUsquK

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

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 197

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