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

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

Run · verification · program 10

Run 79

The enclave's verification of commit 41'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) · low0fe4a23afba1…, tag of slot 0: 0fe4a23afba19da52860b442b7e556d84added7b2720aa955092f160514afaa7

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

7e6687b67986cb07…

Request sha256

16e11ee4230f0da9…

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

Output sha256

b4563366ebff698c…

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:08:26 UTCHaBEB7A5…

Answered

2026-11-08 09:08:40 UTC14 s after it was requestedHaBEB7A5…

Commit

Commit 41

Program

Program 10round 0

Paid for by

practice.antibody.testnet the practice vending contract

Signed by

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

Violationvault keeps its ether · low

receipt 7e6687b67986…

Timeline

Every step is a NEAR transaction, timed by block from commit 41'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-03.practice.antibody.testnet).
225NM7BL…, NEAR transaction: 225NM7BLZdJzFSsQzbHAgBvo6mBxRDB5sNvasoJGAMig, opens an explorer in a new tab2026-11-0809:08:25 UTC · block 276,755,376
+1.8 s after the commit's block
Revealed · run 79 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 16e11ee4230f…, request sha256: 16e11ee4230f0da932bb48d6a447be43d809f0f263cffe8f434a783adee0e860). 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 7e6687b67986…, receipt sha256: 7e6687b67986cb0755ce3edc657882aec81be3b5dde888bdd89e30eea5d8af9f. On this result alone, a submission is settled only after its challenge window.

Delivered in HaBEB7A5…, NEAR transaction: HaBEB7A55KgXgRM21B1tZXwJez9tyWSDSLNvG8mWQiju, opens an explorer in a new tab

Check it yourself

antibody status --run 79

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

{
  "commit": 41,
  "id": 79,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1794128920,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "72f020e9e4e5a698a7e143ea2510c1ebf42e0672b741fe319978f030beefddf050a954db77ebd20f7f7971d2270520fb0032e960a9b306326b90eebb"
          }
        },
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "0fe4a23afba19da52860b442b7e556d84added7b2720aa955092f160514afaa7"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "7e6687b67986cb0755ce3edc657882aec81be3b5dde888bdd89e30eea5d8af9f"
      },
      "output_sha256": "b4563366ebff698c1dfda4779697bb78a034bc212dd13cf5bad2895d3b31cec1",
      "tier": "T1"
    }
  },
  "payer": "practice.antibody.testnet",
  "program": 10,
  "request_sha256": "16e11ee4230f0da932bb48d6a447be43d809f0f263cffe8f434a783adee0e860",
  "round": 0,
  "signer": "m11080904-03.practice.antibody.testnet",
  "started_at": 1794128906
}

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

Check it yourself

tx HaBEB7A55K… · NEAR archival RPC

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

outlayer-verify tx HaBEB7A55KgXgRM21B1tZXwJez9tyWSDSLNvG8mWQiju

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

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 79

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