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

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

Run · verification · program 13

Run 183

The enclave's verification of commit 84'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) · lowba3b7b9d03ff…, tag of slot 0: ba3b7b9d03ffc9856d37b1a69139b982862175d907616e3c191c9294998fbeb7

Impact

$2.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

d06bdcbdc821a111…

Request sha256

8713716ea2cd8389…

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

Output sha256

99e27122187c1b2d…

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-09 00:44:13 UTC392N8XTs…

Answered

2026-11-09 00:44:28 UTC15 s after it was requested392N8XTs…

Commit

Commit 84

Program

Program 13round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

j5hpta.practice.antibody.testnet a visitor's practice try

Violationvault keeps its ether · low

receipt d06bdcbdc821…

Timeline

Every step is a NEAR transaction, timed by block from commit 84'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 (j5hpta.practice.antibody.testnet).
7ML9zFwi…, NEAR transaction: 7ML9zFwisNosXxPZA5za8dLDXU6EmeeqRvcaRRqEx15j, opens an explorer in a new tab2026-11-0900:44:10 UTC · block 276,849,876
+2.4 s after the commit's block
Revealed · run 183 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 8713716ea2cd…, request sha256: 8713716ea2cd838933e59e1bc6025ff608a826e057f9ff77546da0bf59f94c7a). 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 d06bdcbdc821…, receipt sha256: d06bdcbdc821a111fce064caada01b7078187063d6b3cba30e9c080a04decc14. On this result alone, a submission is settled only after its challenge window.

Delivered in 392N8XTs…, NEAR transaction: 392N8XTsTtuLmtRc6Fg57kgwxvDpnfTsamkAMuCKvRCW, opens an explorer in a new tab

Check it yourself

antibody status --run 183

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

{
  "commit": 84,
  "id": 183,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794185068,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "f66106308ac21f15ff14b8a1745ee412e57be99b4a42b24b0444bba0d396baa6acd8be5ff24f3a1db618698bca819d9456762e04487e10be37ffe6ad"
          }
        },
        "impact_usd_micro": "2000000",
        "keys": [
          {
            "slot": 0,
            "tag": "ba3b7b9d03ffc9856d37b1a69139b982862175d907616e3c191c9294998fbeb7"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "d06bdcbdc821a111fce064caada01b7078187063d6b3cba30e9c080a04decc14"
      },
      "output_sha256": "99e27122187c1b2dbcaebcdf3916957ac47a735c9e025571d6536d6c3792e10e",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 13,
  "request_sha256": "8713716ea2cd838933e59e1bc6025ff608a826e057f9ff77546da0bf59f94c7a",
  "round": 0,
  "signer": "j5hpta.practice.antibody.testnet",
  "started_at": 1794185053
}

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

Check it yourself

tx 392N8XTsTt… · NEAR archival RPC

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

outlayer-verify tx 392N8XTsTtuLmtRc6Fg57kgwxvDpnfTsamkAMuCKvRCW

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

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 183

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