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

Run 66 · verification · Violation · Enclave verdict · Antibody

Run · verification · program 6

Run 66

The enclave's verification of commit 32's sealed proof: Violation of the “vault keeps its ether” rule.

ViolationEnclave verdict

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) · low0dcba24fe169…, tag of slot 0: 0dcba24fe1693d9b35e78967d7a6817a02325aceaa5eacc697209bab8692800a

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

Enclave verdict

Receipt sha256

21c1772d9fedef80…

Request sha256

4c31388d76d7b290…

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

Output sha256

75127c4d0edcb805…

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 20:23:19 UTCDsEGrTSy…

Answered

2026-11-07 20:23:34 UTC15 s after it was requestedDsEGrTSy…

Commit

Commit 32

Program

Program 6round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

scrn-k7q2-1107.practice.antibody.testnet our screener dry run

Violationvault keeps its ether · low

receipt 21c1772d9fed…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.0001 wNEAR bond, by our screener dry run (scrn-k7q2-1107.practice.antibody.testnet).
DgfKaBG8…, NEAR transaction: DgfKaBG8S4kPXHQpyDggCP3zQQtXynBsRX32jVMJK3Ns, opens an explorer in a new tab2026-11-0720:23:16 UTC · block 276,679,092
+2.5 s after the commit's block
Revealed · run 66 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 4c31388d76d7…, request sha256: 4c31388d76d7b290882ae4fb736252277dab5ab7b846604b8163186ae341a18c). 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 21c1772d9fed…, receipt sha256: 21c1772d9fedef80d988dca84b0218cabd986ce55904ac91c3ae1947903ab945. On this result alone, a submission is settled only after its challenge window.

Delivered in DsEGrTSy…, NEAR transaction: DsEGrTSyrhQMdohx7eeRPFWbZxwJvK3BfVJbbBahcYgW, opens an explorer in a new tab

Check it yourself

antibody status --run 66

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

{
  "commit": 32,
  "id": 66,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794083014,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "a4cd60799338e29cbff5cee10dda214e184bb2772add0869f8542c59338de7a17b3de3aaa1a16a00056a3ffd4607b1aa5abff0ade8980a68103ecbc0"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "0dcba24fe1693d9b35e78967d7a6817a02325aceaa5eacc697209bab8692800a"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "21c1772d9fedef80d988dca84b0218cabd986ce55904ac91c3ae1947903ab945"
      },
      "output_sha256": "75127c4d0edcb805f36beb88e5c863775b9dcdc933072d6b0cae0aceffc34a57",
      "tier": "T0"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 6,
  "request_sha256": "4c31388d76d7b290882ae4fb736252277dab5ab7b846604b8163186ae341a18c",
  "round": 0,
  "signer": "scrn-k7q2-1107.practice.antibody.testnet",
  "started_at": 1794082999
}

Attested on NEARnot yet

Its Intel TDX quote, verified on NEAR

Not attested on NEAR: the verdict stands on the enclave's result and its challenge window. Our attestation relayer sends each answered run's quote, and anyone may.

Check it yourself

tx DsEGrTSyrh… · NEAR archival RPC

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

outlayer-verify tx DsEGrTSyrhQMdohx7eeRPFWbZxwJvK3BfVJbbBahcYgW

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

Holds if: the run's answer is the enclave's result, not attested

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 66

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