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

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

Run · verification · program 5

Run 39

The enclave's verification of commit 19'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: 770de66a2d91f7e2…, receipt sha256: 770de66a2d91f7e2654569e3888ab68ef03d07849ef4610f3c0674f9a3096ac8
Request sha256: d624457fca67ef02…, request sha256: d624457fca67ef023a7f8802cef07cfd1127bac5f39c8547c5a60dcefdc507a3
The SHA-256 of the input near-antibody sent the enclave: its result and its attestation bind to the same bytes.
Output sha256: 4584a21926c54529…, output sha256: 4584a21926c54529caee8d6ed5855ffd5d57f1a681fe170693d025a1dbe8682b
The SHA-256 of the facts near-antibody received: the TDX quote binds it.
Mode extras: none
Started: 2026-11-04 15:49:43 UTC7hSWWNJb…, NEAR transaction: 7hSWWNJbDfanqsPmEMFhRDdg2KYv42uzpvig5SB5bgzk, opens an explorer in a new tab
Answered: 2026-11-04 15:49:56 UTC13 s after it was requested7hSWWNJb…, NEAR transaction: 7hSWWNJbDfanqsPmEMFhRDdg2KYv42uzpvig5SB5bgzk, opens an explorer in a new tab
Commit: Commit 19
Program: Program 5round 0
Paid for by: agent-g.antibody.testnet, account: agent-g.antibody.testnet our fixture agent G

No violationno rule broken

receipt 770de66a2d91…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.001 wNEAR bond, by our fixture agent G (agent-g.antibody.testnet). Nobody, the project included, can read it before its verdict.
8S2QVg9s…, NEAR transaction: 8S2QVg9snxcewMhewuUUHncVj7pexQRsQ6Deh63MUTpu, opens an explorer in a new tab2026-11-0415:49:31 UTC · block 276,215,510
+12.4 s after the commit's block
Revealed · run 39 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 d624457fca67…, request sha256: d624457fca67ef023a7f8802cef07cfd1127bac5f39c8547c5a60dcefdc507a3).

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

Delivered in 7hSWWNJb…, NEAR transaction: 7hSWWNJbDfanqsPmEMFhRDdg2KYv42uzpvig5SB5bgzk, opens an explorer in a new tab

Check it yourself

antibody status --run 39

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

{
  "commit": 19,
  "id": 39,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1793807396,
      "facts": {
        "extra": "None",
        "impact_usd_micro": "0",
        "keys": [],
        "kind": "NoViolation",
        "protected_harm_usd_micro": "5000000000",
        "reason": null,
        "receipt_sha256": "770de66a2d91f7e2654569e3888ab68ef03d07849ef4610f3c0674f9a3096ac8"
      },
      "output_sha256": "4584a21926c54529caee8d6ed5855ffd5d57f1a681fe170693d025a1dbe8682b",
      "tier": "T1"
    }
  },
  "payer": "agent-g.antibody.testnet",
  "program": 5,
  "request_sha256": "d624457fca67ef023a7f8802cef07cfd1127bac5f39c8547c5a60dcefdc507a3",
  "round": 0,
  "signer": "agent-g.antibody.testnet",
  "started_at": 1793807383
}

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

Check it yourself

tx 7hSWWNJbDf… · NEAR archival RPC

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

outlayer-verify tx 7hSWWNJbDfanqsPmEMFhRDdg2KYv42uzpvig5SB5bgzk

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

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 39

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