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

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

Run · verification · program 12

Run 98

The enclave's verification of commit 57'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: $33.48 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: bee0cff95c14e0b8…, receipt sha256: bee0cff95c14e0b8b925f0a5f2173357fb45802ca841effcc3b23820b28be39a
Request sha256: 9498f840bb1b52c4…, request sha256: 9498f840bb1b52c465b0716b6a9ae7e515c7ad0465723bc4e8497150cff6a227
The SHA-256 of the input near-antibody sent the enclave: its result and its attestation bind to the same bytes.
Output sha256: 98b95adce9815883…, output sha256: 98b95adce98158831d340c001a85168b8e465c7054356868b8955484f0ae3733
The SHA-256 of the facts near-antibody received: the TDX quote binds it.
Mode extras: none
Started: 2026-11-08 17:12:17 UTC7VANT9kR…, NEAR transaction: 7VANT9kRpWGbU7ZJ5rozTWn1sZSCU3qzhh2fysQdDEg6, opens an explorer in a new tab
Answered: 2026-11-08 17:12:31 UTC14 s after it was requested7VANT9kR…, NEAR transaction: 7VANT9kRpWGbU7ZJ5rozTWn1sZSCU3qzhh2fysQdDEg6, opens an explorer in a new tab
Commit: Commit 57
Program: Program 12round 0
Paid for by: agent-c.antibody.testnet, account: agent-c.antibody.testnet our fixture agent C

No violationno rule broken

receipt bee0cff95c14…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.001 wNEAR bond, by our fixture agent C (agent-c.antibody.testnet). Nobody, the project included, can read it before its verdict.
6u8TjVF6…, NEAR transaction: 6u8TjVF6TkYFWek7QBmxAbP4FdhHWzJXP72jSUpMkTfn, opens an explorer in a new tab2026-11-0817:11:58 UTC · block 276,804,671
+18.8 s after the commit's block
Revealed · run 98 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 9498f840bb1b…, request sha256: 9498f840bb1b52c465b0716b6a9ae7e515c7ad0465723bc4e8497150cff6a227).

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

Delivered in 7VANT9kR…, NEAR transaction: 7VANT9kRpWGbU7ZJ5rozTWn1sZSCU3qzhh2fysQdDEg6, opens an explorer in a new tab

Check it yourself

antibody status --run 98

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

{
  "commit": 57,
  "id": 98,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794157951,
      "facts": {
        "extra": "None",
        "impact_usd_micro": "33480361",
        "keys": [],
        "kind": "NoViolation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "bee0cff95c14e0b8b925f0a5f2173357fb45802ca841effcc3b23820b28be39a"
      },
      "output_sha256": "98b95adce98158831d340c001a85168b8e465c7054356868b8955484f0ae3733",
      "tier": "T1"
    }
  },
  "payer": "agent-c.antibody.testnet",
  "program": 12,
  "request_sha256": "9498f840bb1b52c465b0716b6a9ae7e515c7ad0465723bc4e8497150cff6a227",
  "round": 0,
  "signer": "agent-c.antibody.testnet",
  "started_at": 1794157937
}

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

Check it yourself

tx 7VANT9kRpW… · NEAR archival RPC

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

outlayer-verify tx 7VANT9kRpWGbU7ZJ5rozTWn1sZSCU3qzhh2fysQdDEg6

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

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 98

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