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

Run 71 · verification · Violation · Attested on NEAR · Antibody

Run · verification · program 9

Run 71

The enclave's verification of commit 35's sealed proof: Violation of the solvency rule.

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

Violation

Keys

slot 0 (solvency) · criticalf27ef2619b52…, tag of slot 0: f27ef2619b5207bffc2d5b34d0476b8e4cdf60fe6884c20d357774a5c3bfc4f6

Impact

$462,931.85 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

60f61ceebdfb2cbd…

Request sha256

f0247ae4b13b511f…

The SHA-256 of the input near-antibody sent the enclave: its result and its attestation bind to the same bytes.

Output sha256

ba4ecf40a6f05f86…

The SHA-256 of the facts near-antibody received: the TDX quote binds it.

Mode extras

a disclosure wrap (wrap_d): if its tag and round are disclosed, their key opens the proof

Started

2026-11-08 02:40:13 UTC2Bf74vNQ…

Answered

2026-11-08 02:40:29 UTC16 s after it was requested2Bf74vNQ…

Commit

Commit 35

Program

Program 9round 0

Paid for by

agent-a.antibody.testnet our fixture agent A

Violationsolvency · critical

receipt 60f61ceebdfb…

Timeline

Every step is a NEAR transaction, timed by block from commit 35'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.
HCViXsoK…, NEAR transaction: HCViXsoKwd9KLzURGRV3igzY5vsccNwcDnn7cRYWHqpV, opens an explorer in a new tab2026-11-0802:38:24 UTC · block 276,716,052
+108.8 s after the commit's block
Revealed · run 71 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 f0247ae4b13b…, request sha256: f0247ae4b13b511f40dfe5eae9488a993e3f0b2b2d05a07626be5a11eafacee7).

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

Delivered in 2Bf74vNQ…, NEAR transaction: 2Bf74vNQdwGMT8oLf67EquZkXKZLUynXwTHHzAE4euJC, opens an explorer in a new tab

Check it yourself

antibody status --run 71

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

{
  "commit": 35,
  "id": 71,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794105629,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "f76c554b052a61c821c8aaf8aa5d730a9da771d3f7c181f219fc93958fa5b5f4df9aa438493ce87459bcd824ceabec034a947ed7edce0b64753fb8e9"
          }
        },
        "impact_usd_micro": "462931853867",
        "keys": [
          {
            "slot": 0,
            "tag": "f27ef2619b5207bffc2d5b34d0476b8e4cdf60fe6884c20d357774a5c3bfc4f6"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "60f61ceebdfb2cbd40153853ef038bf052fbfea3347d862dd06de7580b9f28c1"
      },
      "output_sha256": "ba4ecf40a6f05f86b9dd4bfa208a64c68ae4a406d4785c09c95a8ef8dc39ca5c",
      "tier": "T1"
    }
  },
  "payer": "agent-a.antibody.testnet",
  "program": 9,
  "request_sha256": "f0247ae4b13b511f40dfe5eae9488a993e3f0b2b2d05a07626be5a11eafacee7",
  "round": 0,
  "signer": "agent-a.antibody.testnet",
  "started_at": 1794105613
}

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

Check it yourself

tx 2Bf74vNQdw… · NEAR archival RPC

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

outlayer-verify tx 2Bf74vNQdwGMT8oLf67EquZkXKZLUynXwTHHzAE4euJC

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

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 71

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