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

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

Run · verification · program 12

Run 101

The enclave's verification of commit 60'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) · criticalaa08b93ae815…, tag of slot 0: aa08b93ae815a96d0ed7d13d6e8511bf249999f9c512a1fc9d3f0728a5765df6

Impact

$10,400.00 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

75bb8acf44959a4b…

Request sha256

0f8003dcdefe054a…

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

Output sha256

5360105a843e2dd9…

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 17:14:49 UTCZEtfQe8C…

Answered

2026-11-08 17:15:05 UTC16 s after it was requestedZEtfQe8C…

Commit

Commit 60

Program

Program 12round 0

Paid for by

agent-f.antibody.testnet our fixture agent F

Violationsolvency · critical

receipt 75bb8acf4495…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.001 wNEAR bond, by our fixture agent F (agent-f.antibody.testnet). Nobody, the project included, can read it before its verdict.
9KvRqDuY…, NEAR transaction: 9KvRqDuYBubWDTX9ArbrExifpq5PNKw7xdAsFG6BYYn, opens an explorer in a new tab2026-11-0817:14:42 UTC · block 276,804,942
+6.6 s after the commit's block
Revealed · run 101 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 0f8003dcdefe…, request sha256: 0f8003dcdefe054aadcaf71bfece53aabcb4be1d8ae0aef86f28fcd93061a57d).

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

Delivered in ZEtfQe8C…, NEAR transaction: ZEtfQe8CHKFd1xSxPnT3VzGcsEE8egKTaBSL3V8VtCP, opens an explorer in a new tab

Check it yourself

antibody status --run 101

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

{
  "commit": 60,
  "id": 101,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794158105,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "1566d8561154e507b30153e107fd631ebb57ab6c5cf0853a9901898dbbbba3eaad500694528677c9c034ba0594a15e77cfca1d6836a780d2ece56b59"
          }
        },
        "impact_usd_micro": "10400000000",
        "keys": [
          {
            "slot": 0,
            "tag": "aa08b93ae815a96d0ed7d13d6e8511bf249999f9c512a1fc9d3f0728a5765df6"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "75bb8acf44959a4b66cc8a96c52587f01240dccac3004cc4efa9c70056c2f3b5"
      },
      "output_sha256": "5360105a843e2dd9287f7f6ee52f650de0b4b009d67376d831f1ee9ae0dfdb66",
      "tier": "T1"
    }
  },
  "payer": "agent-f.antibody.testnet",
  "program": 12,
  "request_sha256": "0f8003dcdefe054aadcaf71bfece53aabcb4be1d8ae0aef86f28fcd93061a57d",
  "round": 0,
  "signer": "agent-f.antibody.testnet",
  "started_at": 1794158089
}

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

Check it yourself

tx ZEtfQe8CHK… · NEAR archival RPC

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

outlayer-verify tx ZEtfQe8CHKFd1xSxPnT3VzGcsEE8egKTaBSL3V8VtCP

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

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 101

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