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

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

Run · verification · program 12

Run 100

The enclave's verification of commit 59's sealed proof: 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

72b98b45eebcaa11…

Request sha256

060df12108114585…

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

Output sha256

7030e37cacece671…

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:11 UTCCkp7t8Cq…

Answered

2026-11-08 17:14:26 UTC15 s after it was requestedCkp7t8Cq…

Commit

Commit 59

Program

Program 12round 0

Paid for by

agent-e.antibody.testnet our fixture agent E

Violationshare price · medium

receipt 72b98b45eebc…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.001 wNEAR bond, by our fixture agent E (agent-e.antibody.testnet). Nobody, the project included, can read it before its verdict.
5UsSyZ1a…, NEAR transaction: 5UsSyZ1a8M4UiWZp8WoQDCBcb8oFnDtq5pBZMpfPv8Wk, opens an explorer in a new tab2026-11-0817:13:52 UTC · block 276,804,860
+18.9 s after the commit's block
Revealed · run 100 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 060df1210811…, request sha256: 060df121081145858f783578b1fae28c6d38b0a4057b8b693747fffa4bf3d023).

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

Delivered in Ckp7t8Cq…, NEAR transaction: Ckp7t8CqNezt4WgDqC8Z7Fv1JePucNq9kGrQ1VANoYh5, opens an explorer in a new tab

Check it yourself

antibody status --run 100

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

{
  "commit": 59,
  "id": 100,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794158066,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "1415616b8ef330ddf83175b899929023521950754bcfddd80d772b5355416e124b36f97db5f9bdfb6b043337f48d8c8fa6469375a8b9cd0fec7b9115"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 2,
            "tag": "24f13596550fd4e2cf6c6bbaad7a7330bf656e6832b81db6e5c7adf1f26fc1c2"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "72b98b45eebcaa11406ecdb53e528424e176b88f2fac913015252648dd0227bc"
      },
      "output_sha256": "7030e37cacece6712bf437c96661c831b2d84ccdecb34292a0dbac5c373fcc53",
      "tier": "T1"
    }
  },
  "payer": "agent-e.antibody.testnet",
  "program": 12,
  "request_sha256": "060df121081145858f783578b1fae28c6d38b0a4057b8b693747fffa4bf3d023",
  "round": 0,
  "signer": "agent-e.antibody.testnet",
  "started_at": 1794158051
}

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

Check it yourself

tx Ckp7t8CqNe… · NEAR archival RPC

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

outlayer-verify tx Ckp7t8CqNezt4WgDqC8Z7Fv1JePucNq9kGrQ1VANoYh5

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

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 100

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