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

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

Run · verification · program 6

Run 58

The enclave's verification of commit 24'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) · low3d033ead15c6…, tag of slot 0: 3d033ead15c63a63185e5b4535711b803aeb7bc41a65009f713c584be316f78b

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

28245200223fe2ef…

Request sha256

d41c873569166815…

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

Output sha256

ab3d3b01c2078a0a…

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-07 11:18:18 UTCFRD9CkrR…

Answered

2026-11-07 11:18:33 UTC15 s after it was requestedFRD9CkrR…

Commit

Commit 24

Program

Program 6round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

judge-lrb2.practice.antibody.testnet a visitor's practice try

Violationvault keeps its ether · low

receipt 28245200223f…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.0001 wNEAR bond, by a visitor's practice try (judge-lrb2.practice.antibody.testnet).
7mgmi2hb…, NEAR transaction: 7mgmi2hbQX26kaPvJJzp2NxHktoq8BWSMSwEM19NRUsD, opens an explorer in a new tab2026-11-0711:18:15 UTC · block 276,623,774
+2.5 s after the commit's block
Revealed · run 58 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 d41c87356916…, request sha256: d41c873569166815ce2ec57cbafa209214eb4003107896bd614af4f8c9d53ba9). 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 28245200223f…, receipt sha256: 28245200223fe2efda22e2031910c497e60bbade0e7dcdcd3a3f33dc69cb1dec. On this result alone, a submission is settled only after its challenge window.

Delivered in FRD9CkrR…, NEAR transaction: FRD9CkrR2xKQWFm4JuiWrsSzZqTtiNpko3CKCYmtW13Y, opens an explorer in a new tab

Check it yourself

antibody status --run 58

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

{
  "commit": 24,
  "id": 58,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794050313,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "db89aa5d3f0d45b8c7835b31503c987809fd4b584e456bac9420852c88ccac167f5c85449138fbb60e3a6ffc6376803e7eadbefdbcbc91cc1b181f6b"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "3d033ead15c63a63185e5b4535711b803aeb7bc41a65009f713c584be316f78b"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "28245200223fe2efda22e2031910c497e60bbade0e7dcdcd3a3f33dc69cb1dec"
      },
      "output_sha256": "ab3d3b01c2078a0af129c5392afc7bc7ed6469e12cfda5389bf532b1ecc41d55",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 6,
  "request_sha256": "d41c873569166815ce2ec57cbafa209214eb4003107896bd614af4f8c9d53ba9",
  "round": 0,
  "signer": "judge-lrb2.practice.antibody.testnet",
  "started_at": 1794050298
}

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

Check it yourself

tx FRD9CkrR2x… · NEAR archival RPC

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

outlayer-verify tx FRD9CkrR2xKQWFm4JuiWrsSzZqTtiNpko3CKCYmtW13Y

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

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 58

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