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

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

Run · verification · program 12

Run 95

The project's sealed declaration of a known issue for program 12, 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) · medium24f13596550f…, tag of slot 2: 24f13596550fd4e2cf6c6bbaad7a7330bf656e6832b81db6e5c7adf1f26fc1c2

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

7499bb7341c0c1ad…

Request sha256

8dc35485b8a67797…

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

Output sha256

1b513939ffd6f2a5…

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

Mode extras

none

Started

2026-11-08 16:54:21 UTC9oHgd4bc…

Answered

2026-11-08 16:54:35 UTC14 s after it was requested9oHgd4bc…

Commit

none: this run is the program's own

Program

Program 12round 0

Paid for by

acme.antibody.testnet the program's project

Violationshare price · medium

receipt 7499bb7341c0…

Timeline

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

0.0 s (the run's request)
Run 95 requested
Requested and paid for by the project (acme.antibody.testnet).
9oHgd4bc…, NEAR transaction: 9oHgd4bcgxCu6tNrZfSKCdDgF5WsiWJwGWBD5vaiTGk1, opens an explorer in a new tab2026-11-0816:54:21 UTC · block 276,802,894
+13.7 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 7499bb7341c0…, receipt sha256: 7499bb7341c0c1ade2a96c7f9cab93a2e58d0dff7efaf0a9c3109e3f61c6b049

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

Delivered in 9oHgd4bc…, NEAR transaction: 9oHgd4bcgxCu6tNrZfSKCdDgF5WsiWJwGWBD5vaiTGk1, opens an explorer in a new tab

Check it yourself

antibody status --run 95

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

{
  "commit": null,
  "id": 95,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794156875,
      "facts": {
        "extra": "None",
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 2,
            "tag": "24f13596550fd4e2cf6c6bbaad7a7330bf656e6832b81db6e5c7adf1f26fc1c2"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "7499bb7341c0c1ade2a96c7f9cab93a2e58d0dff7efaf0a9c3109e3f61c6b049"
      },
      "output_sha256": "1b513939ffd6f2a57f51d7a33da4e13846d7f075ca7daa4382b7b2f0dedfb0d2",
      "tier": "T1"
    }
  },
  "payer": "acme.antibody.testnet",
  "program": 12,
  "request_sha256": "8dc35485b8a677974e25efe9860ef23fc624599687ef91aac06eceed4b3235bc",
  "round": 0,
  "signer": "acme.antibody.testnet",
  "started_at": 1794156861
}

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

Check it yourself

tx 9oHgd4bcgx… · NEAR archival RPC

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

outlayer-verify tx 9oHgd4bcgxCu6tNrZfSKCdDgF5WsiWJwGWBD5vaiTGk1

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

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 95

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