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

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

Run · verification · program 5

Run 32

The project's sealed declaration of a known issue for program 5, checked in the enclave before the program opened: Violation of the “share price” 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 2 (share_price) · medium45b2dc90a6a1…, tag of slot 2: 45b2dc90a6a1182df8596d4205f3d0e69771aa87dcd0fb7e9d9e1e5505f6d8c5

Impact

$0.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

3d11e9031373ea63…

Request sha256

d736090fb74b12cc…

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

Output sha256

5633b0e1e12fca16…

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

Mode extras

none

Started

2026-11-04 15:40:37 UTCBbseTTCw…

Answered

2026-11-04 15:40:53 UTC16 s after it was requestedBbseTTCw…

Commit

none: this run is the program's own

Program

Program 5round 0

Paid for by

acme.antibody.testnet the program's project

Violationshare price · medium

receipt 3d11e9031373…

Timeline

Every step is a NEAR transaction, timed by block from the run's request.

0.0 s (the run's request)
Run 32 requested
Requested and paid for by the project (acme.antibody.testnet).
BbseTTCw…, NEAR transaction: BbseTTCwsoUup6iMxvy1G8N9fM71BS56yB3XodmyKReL, opens an explorer in a new tab2026-11-0415:40:37 UTC · block 276,214,579
+15.8 s after the run's request
Enclave verdict: violation of the “share price” rule
OutLayer's operator delivered the enclave's output to near-antibody. Receipt 3d11e9031373…, receipt sha256: 3d11e9031373ea6379b7bba5cc25060bc1d690f3ba237094ce9f694217ab9fe4

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

Delivered in BbseTTCw…, NEAR transaction: BbseTTCwsoUup6iMxvy1G8N9fM71BS56yB3XodmyKReL, opens an explorer in a new tab

Check it yourself

antibody status --run 32

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

{
  "commit": null,
  "id": 32,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1793806853,
      "facts": {
        "extra": "None",
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 2,
            "tag": "45b2dc90a6a1182df8596d4205f3d0e69771aa87dcd0fb7e9d9e1e5505f6d8c5"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "3d11e9031373ea6379b7bba5cc25060bc1d690f3ba237094ce9f694217ab9fe4"
      },
      "output_sha256": "5633b0e1e12fca163e76e6da9641c69a0707245b8fac17ba278256ed12cb1c7d",
      "tier": "T1"
    }
  },
  "payer": "acme.antibody.testnet",
  "program": 5,
  "request_sha256": "d736090fb74b12cc6fc5a2093795c2f44229ac68a1ea939df22e88f6388098c8",
  "round": 0,
  "signer": "acme.antibody.testnet",
  "started_at": 1793806837
}

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

Check it yourself

tx BbseTTCwso… · NEAR archival RPC

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

outlayer-verify tx BbseTTCwsoUup6iMxvy1G8N9fM71BS56yB3XodmyKReL

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

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 32

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