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

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

Run · verification · program 10

Run 74

The enclave's verification of commit 37'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) · lowccf8c5191bb9…, tag of slot 0: ccf8c5191bb97d757c6c88c1d7c3a6b2fd20bc0c47018a3f4c564c23d97eb543

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

0219ea4a1187425b…

Request sha256

727aa8b76f600021…

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

Output sha256

182237db1465f4bb…

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 08:24:16 UTC4fcjSJcs…

Answered

2026-11-08 08:24:29 UTC13 s after it was requested4fcjSJcs…

Commit

Commit 37

Program

Program 10round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

judge-2-p10.practice.antibody.testnet our check of a fresh practice program

Violationvault keeps its ether · low

receipt 0219ea4a1187…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.0001 wNEAR bond, by our check of a fresh practice program (judge-2-p10.practice.antibody.testnet).
32SpqfBw…, NEAR transaction: 32SpqfBwXwUzNhyaZdzfsfqzZe8KwR7kkR5B3Ut3cUBp, opens an explorer in a new tab2026-11-0808:24:14 UTC · block 276,750,877
+2.5 s after the commit's block
Revealed · run 74 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 727aa8b76f60…, request sha256: 727aa8b76f600021d4df028784d7ca929669b35079cbcd2dbd6eae273706e7a1). 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 0219ea4a1187…, receipt sha256: 0219ea4a1187425b7d8b8fc848bfbcfc6984b629fce4d86e39df4f0a5f33c0d3. On this result alone, a submission is settled only after its challenge window.

Delivered in 4fcjSJcs…, NEAR transaction: 4fcjSJcsyDEMRHx1n4PUD6exoKfWjqPv8VZjJycjksMA, opens an explorer in a new tab

Check it yourself

antibody status --run 74

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

{
  "commit": 37,
  "id": 74,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794126269,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "a05fae35c91186c470ec3d26623b5c7f088b95a381383e9ade22f4b90ca420a856b6cc99e81188bd366bddb1f100f7f1a51c02a8a29e5bf29d11e45a"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "ccf8c5191bb97d757c6c88c1d7c3a6b2fd20bc0c47018a3f4c564c23d97eb543"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "0219ea4a1187425b7d8b8fc848bfbcfc6984b629fce4d86e39df4f0a5f33c0d3"
      },
      "output_sha256": "182237db1465f4bb28a9cfb543b7a8aca765cd4aeb86486b86b439b1a6353ec6",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 10,
  "request_sha256": "727aa8b76f600021d4df028784d7ca929669b35079cbcd2dbd6eae273706e7a1",
  "round": 0,
  "signer": "judge-2-p10.practice.antibody.testnet",
  "started_at": 1794126256
}

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

Check it yourself

tx 4fcjSJcsyD… · NEAR archival RPC

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

outlayer-verify tx 4fcjSJcsyDEMRHx1n4PUD6exoKfWjqPv8VZjJycjksMA

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

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 74

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