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

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

Run · verification · program 10

Run 77

The enclave's verification of commit 39'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) · low683215c3927d…, tag of slot 0: 683215c3927d5aa76c8ef5ed7d78e7ac0208b25456eeab5692ed54c1bf601c06

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

79ff7245a11929d9…

Request sha256

828effbd878cce53…

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

Output sha256

97e84e992fcffa52…

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:06:02 UTCAUjrNQgv…

Answered

2026-11-08 09:06:15 UTC13 s after it was requestedAUjrNQgv…

Commit

Commit 39

Program

Program 10round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

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

Violationvault keeps its ether · low

receipt 79ff7245a119…

Timeline

Every step is a NEAR transaction, timed by block from commit 39'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-01.practice.antibody.testnet).
8tWGvsu1…, NEAR transaction: 8tWGvsu1zxumPbvAiKvwj1wPmENqZTo3YX4B1T15gEkd, opens an explorer in a new tab2026-11-0809:06:00 UTC · block 276,755,132
+2.4 s after the commit's block
Revealed · run 77 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 828effbd878c…, request sha256: 828effbd878cce5355e32d17c57cd3c4849091e32e1a79b6375b0b658674c1a2). 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 79ff7245a119…, receipt sha256: 79ff7245a11929d9544486b7758c104b855eb1614e4855195dd62fcb9cc325bd. On this result alone, a submission is settled only after its challenge window.

Delivered in AUjrNQgv…, NEAR transaction: AUjrNQgvCAWpwPnzW3sHGtjnw8jrZQwEeRxhNNz7apUm, opens an explorer in a new tab

Check it yourself

antibody status --run 77

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

{
  "commit": 39,
  "id": 77,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794128775,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "9b4515f14a7af71908de9e19d5813d2a20c009b38c528fd62272b8975aed142fe7efba2ee46db0305fce956cf8d5038c6467e8db1c9a6e1277d4854b"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "683215c3927d5aa76c8ef5ed7d78e7ac0208b25456eeab5692ed54c1bf601c06"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "79ff7245a11929d9544486b7758c104b855eb1614e4855195dd62fcb9cc325bd"
      },
      "output_sha256": "97e84e992fcffa52681df42ed15020f5f394c95e73b405d2d821a07939d9b3d2",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 10,
  "request_sha256": "828effbd878cce5355e32d17c57cd3c4849091e32e1a79b6375b0b658674c1a2",
  "round": 0,
  "signer": "m11080904-01.practice.antibody.testnet",
  "started_at": 1794128762
}

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

Check it yourself

tx AUjrNQgvCA… · NEAR archival RPC

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

outlayer-verify tx AUjrNQgvCAWpwPnzW3sHGtjnw8jrZQwEeRxhNNz7apUm

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

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 77

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