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

Run 103 · release wrap · Attested on NEAR · Antibody

Run · release wrap · program 12

Run 103

The release wrap for commit 55: after payment, the proof's content key wrapped to the project's own key, so the project reads exactly what it paid for.

answeredAttested on NEAR

What the enclave answered

The run as near-antibody records it: a release wrap's output, not a verdict. Every hash below is checkable against NEAR.

Mode: release_wrap
A release wrap: after payment, the proof's content key wrapped to the project's own key.
What it produced: The proof's content key, wrapped to the project's key (acme.antibody.testnet): 80 bytes 185d0b6ce04457d0…, the release wrap: 185d0b6ce04457d0cc583fa02fff7fcdc5e55f4bb4f9626eb5b72155b1230003a62924eb53bdc0700a23a6a0132b3769418b910c365c9c2071b2af5de0079eaa0c8de49570e3b2219dc1532e4a8e7b31Only the project's key opens it: antibody program read unwraps the content key, opens the proof and re-runs it locally.
Not a verdict: this run does not judge a proof, so it has no kind, keys or impact of its own.
Level: Attested on NEAR
Receipt sha256: 9e606a4ed3a5537e…, receipt sha256: 9e606a4ed3a5537e4040c36d58beabfd843368917073f0ddc586df620eb55c29
Request sha256: af06e0da1eccd0fb…, request sha256: af06e0da1eccd0fb6f2107e559796865e07012880c1426e8cd4b5e72498f85d0
The SHA-256 of the input near-antibody sent the enclave: its result and its attestation bind to the same bytes.
Output sha256: 54affa1ebc79265c…, output sha256: 54affa1ebc79265c0d2589c98af408bb0e4e4660c9d967b581de34b9c6e6f152
The SHA-256 of the facts near-antibody received: the TDX quote binds it.
Started: 2026-11-08 17:18:36 UTCD7ys1rCR…, NEAR transaction: D7ys1rCRrF195doSGpNjBNNZSRWza3m7DA4nkoo7kp3R, opens an explorer in a new tab
Answered: 2026-11-08 17:18:52 UTC16 s after it was requestedD7ys1rCR…, NEAR transaction: D7ys1rCRrF195doSGpNjBNNZSRWza3m7DA4nkoo7kp3R, opens an explorer in a new tab
Commit: Commit 55
Program: Program 12round 0
Paid for by: acme.antibody.testnet, account: acme.antibody.testnet the program's project

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.001 wNEAR bond, by our fixture agent A (agent-a.antibody.testnet). Nobody, the project included, can read it before its verdict.
9DYyLTyN…, NEAR transaction: 9DYyLTyNMcwmUj1eApUpnAsnG6WMkM2DehUUc9RAoF6W, opens an explorer in a new tab2026-11-0817:08:21 UTC · block 276,804,312
+10.2 min after the commit's block
Release wrap requested · run 103
The project (acme.antibody.testnet) asked the enclave to wrap this proof's content key to the project's own key.
D7ys1rCR…, NEAR transaction: D7ys1rCRrF195doSGpNjBNNZSRWza3m7DA4nkoo7kp3R, opens an explorer in a new tab

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: the proof's content key, wrapped to the project's key, receipt 9e606a4ed3a5…, receipt sha256: 9e606a4ed3a5537e4040c36d58beabfd843368917073f0ddc586df620eb55c29. A release wrap judges no proof: its answer is not a verdict.

Delivered in D7ys1rCR…, NEAR transaction: D7ys1rCRrF195doSGpNjBNNZSRWza3m7DA4nkoo7kp3R, opens an explorer in a new tab

Check it yourself

antibody status --run

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

{
  "commit": 55,
  "id": 103,
  "mode": "release_wrap",
  "outcome": {
    "Answered": {
      "at": 1794158332,
      "facts": {
        "extra": {
          "Wrap": {
            "wrap": "185d0b6ce04457d0cc583fa02fff7fcdc5e55f4bb4f9626eb5b72155b1230003a62924eb53bdc0700a23a6a0132b3769418b910c365c9c2071b2af5de0079eaa0c8de49570e3b2219dc1532e4a8e7b31"
          }
        },
        "impact_usd_micro": "0",
        "keys": [],
        "kind": "NoViolation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "9e606a4ed3a5537e4040c36d58beabfd843368917073f0ddc586df620eb55c29"
      },
      "output_sha256": "54affa1ebc79265c0d2589c98af408bb0e4e4660c9d967b581de34b9c6e6f152",
      "tier": "T1"
    }
  },
  "payer": "acme.antibody.testnet",
  "program": 12,
  "request_sha256": "af06e0da1eccd0fb6f2107e559796865e07012880c1426e8cd4b5e72498f85d0",
  "round": 0,
  "signer": "acme.antibody.testnet",
  "started_at": 1794158316
}

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. An attested wrap stands; a wrap no quote attested may be requested again.

Attested in 8tBSidGv…, NEAR transaction: 8tBSidGvSzhXdE6hwpzHLJMQn4Zd49pJvzoCtGTFPm3m, opens an explorer in a new tab

Check it yourself

tx D7ys1rCRrF… · NEAR archival RPC

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

outlayer-verify tx D7ys1rCRrF195doSGpNjBNNZSRWza3m7DA4nkoo7kp3R

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

Holds if: the run is attested: its quote was verified on NEAR

What the enclave answered

Timeline

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