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

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

Run · verification · program 10

Run 80

The enclave's verification of commit 42's sealed proof: Violation of the “vault keeps its ether” 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 (vault_keeps_its_ether) · low237c5048a958…, tag of slot 0: 237c5048a958cdca08d2b3243cdaae09d77527db0c17e0f9b814a4604c9fd7b6

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

ad69f4b4c8c19873…

Request sha256

9137b0a7d3f216f5…

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

Output sha256

7b37e6947d7ef9aa…

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 09:11:22 UTC7LqaGcA6…

Answered

2026-11-08 09:11:36 UTC14 s after it was requested7LqaGcA6…

Commit

Commit 42

Program

Program 10round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

m11080904-04.practice.antibody.testnet a measured agent run (docs/agent-runs.md)

Violationvault keeps its ether · low

receipt ad69f4b4c8c1…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.0001 wNEAR bond, by a measured agent run (docs/agent-runs.md) (m11080904-04.practice.antibody.testnet).
5thLyaYi…, NEAR transaction: 5thLyaYiWXP29jY2WxW7zxX7CZGRFYeBo4nekfVen6Fk, opens an explorer in a new tab2026-11-0809:11:20 UTC · block 276,755,666
+1.8 s after the commit's block
Revealed · run 80 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 9137b0a7d3f2…, request sha256: 9137b0a7d3f216f5844a91515dc52074426731aa979e168366d68edd05facd91). The run was paid for by the practice vending contract (practice.antibody.testnet).

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

Delivered in 7LqaGcA6…, NEAR transaction: 7LqaGcA67tuPvdVFpaT52WymyLGv4UCvmc6PBejVKzYJ, opens an explorer in a new tab

Check it yourself

antibody status --run 80

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

{
  "commit": 42,
  "id": 80,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794129096,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "85c3ca24371446b6c3269ff5c2edece575f93948ede91cdab250133ef97fe75487b83dec78dc9fbe47fc2816b7ad9217853ad9deb22749bee8135052"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "237c5048a958cdca08d2b3243cdaae09d77527db0c17e0f9b814a4604c9fd7b6"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "ad69f4b4c8c1987364671058b9e6493792af4441e1c786eb9dfd3ad298268e39"
      },
      "output_sha256": "7b37e6947d7ef9aa2e3df3c94e711e49ec5b95603f1bc7017a721f7e9306f321",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 10,
  "request_sha256": "9137b0a7d3f216f5844a91515dc52074426731aa979e168366d68edd05facd91",
  "round": 0,
  "signer": "m11080904-04.practice.antibody.testnet",
  "started_at": 1794129082
}

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

Check it yourself

tx 7LqaGcA67t… · NEAR archival RPC

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

outlayer-verify tx 7LqaGcA67tuPvdVFpaT52WymyLGv4UCvmc6PBejVKzYJ

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

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 80

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