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

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

Run · verification · program 0

Run 8

The enclave's verification of commit 6'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: $5,000.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: 3ea56d74f03e1847…, receipt sha256: 3ea56d74f03e184747dd25e0df3c30f261bdb41d4033374425cd3239b6981847
Request sha256: af2114589c267822…, request sha256: af2114589c2678223d0fae7d4a847261567129788f68f6160f46f7d1735a4079
The SHA-256 of the input near-antibody sent the enclave: its result and its attestation bind to the same bytes.
Output sha256: 9d329271cdcb5b31…, output sha256: 9d329271cdcb5b3112cf323145511a9c437ef9fc26acc3cd16a46fbb1c5faaad
The SHA-256 of the facts near-antibody received: the TDX quote binds it.
Mode extras: none
Started: 2026-11-03 11:56:45 UTC
Answered: 2026-11-03 11:57:00 UTC15 s after it was requested
Commit: Commit 6
Program: Program 0round 0
Paid for by: agent-g.antibody.testnet, account: agent-g.antibody.testnet our fixture agent G

No violationno rule broken

receipt 3ea56d74f03e…

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 3ea56d74f03e…, receipt sha256: 3ea56d74f03e184747dd25e0df3c30f261bdb41d4033374425cd3239b6981847. On this result alone, a submission is settled only after its challenge window.

Check it yourself

antibody status --run 8

Attested on NEAR

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

{
  "commit": 6,
  "id": 8,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1793707020,
      "facts": {
        "extra": "None",
        "impact_usd_micro": "0",
        "keys": [],
        "kind": "NoViolation",
        "protected_harm_usd_micro": "5000000000",
        "reason": null,
        "receipt_sha256": "3ea56d74f03e184747dd25e0df3c30f261bdb41d4033374425cd3239b6981847"
      },
      "output_sha256": "9d329271cdcb5b3112cf323145511a9c437ef9fc26acc3cd16a46fbb1c5faaad",
      "tier": "T1"
    }
  },
  "payer": "agent-g.antibody.testnet",
  "program": 0,
  "request_sha256": "af2114589c2678223d0fae7d4a847261567129788f68f6160f46f7d1735a4079",
  "round": 0,
  "signer": "agent-g.antibody.testnet",
  "started_at": 1793707005
}

Check it yourself

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

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

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 8

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

What the enclave answered

How it is checked

What the enclave answered

The raw record

Its Intel TDX quote, verified on NEAR

A zero-knowledge proof of the verdict