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

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

Run · verification · program 10

Run 78

The enclave's verification of commit 40'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) · low57d0a2217579…, tag of slot 0: 57d0a221757991adb38f5d45d42af422ad92c5801d4f06d689de651b1fa5a707

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

de75d231e2b71dcf…

Request sha256

cd145a0831dd9527…

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

Output sha256

5a6da1eb835a7e26…

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:07:13 UTCGD3cjy7f…

Answered

2026-11-08 09:07:24 UTC11 s after it was requestedGD3cjy7f…

Commit

Commit 40

Program

Program 10round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

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

Violationvault keeps its ether · low

receipt de75d231e2b7…

Timeline

Every step is a NEAR transaction, timed by block from commit 40'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-02.practice.antibody.testnet).
8rKmT4vX…, NEAR transaction: 8rKmT4vXKezmA5GwnZxrYZsa92rQBLc2Wr2w21suxQuS, opens an explorer in a new tab2026-11-0809:07:11 UTC · block 276,755,252
+1.9 s after the commit's block
Revealed · run 78 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 cd145a0831dd…, request sha256: cd145a0831dd9527adbc8ed4c323e458e82bac6e791829b305bac6ed18c8e8b6). 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 de75d231e2b7…, receipt sha256: de75d231e2b71dcf651f96e6fb669d396c3d76d6bed4586353a20288ad81dd5b. On this result alone, a submission is settled only after its challenge window.

Delivered in GD3cjy7f…, NEAR transaction: GD3cjy7fn1E6384Y7yaLVnYcP8zTbXAJG8VZj5ckQDPV, opens an explorer in a new tab

Check it yourself

antibody status --run 78

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

{
  "commit": 40,
  "id": 78,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794128844,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "31bf6dbfbb8272035b73e224672fa8d79fc723fa2ead1d986b3764323cace6d445ef3161506a043358f2ae19ae3a7b06466123539aee2b4fea00a99d"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "57d0a221757991adb38f5d45d42af422ad92c5801d4f06d689de651b1fa5a707"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "de75d231e2b71dcf651f96e6fb669d396c3d76d6bed4586353a20288ad81dd5b"
      },
      "output_sha256": "5a6da1eb835a7e26cfdf31f8a4abda8c6d1411013b43fef4f769a092cbd6ee09",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 10,
  "request_sha256": "cd145a0831dd9527adbc8ed4c323e458e82bac6e791829b305bac6ed18c8e8b6",
  "round": 0,
  "signer": "m11080904-02.practice.antibody.testnet",
  "started_at": 1794128833
}

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

Check it yourself

tx GD3cjy7fn1… · NEAR archival RPC

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

outlayer-verify tx GD3cjy7fn1E6384Y7yaLVnYcP8zTbXAJG8VZj5ckQDPV

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

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 78

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