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

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

Run · verification · program 5

Run 34

The enclave's verification of commit 14's sealed proof: Violation of the “fees to treasury” 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 1 (fees_to_treasury) · highae7e21c8af1b…, tag of slot 1: ae7e21c8af1b96023b13ae1daff4bcd1076b5b282e4f6ce6fb91e6fdae5f6de4

Impact

$1,000.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

a1e3123df9034dc7…

Request sha256

64e23a21f48723b8…

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

Output sha256

c930f905588f7c34…

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-04 15:47:30 UTCAdqYNMxc…

Answered

2026-11-04 15:47:44 UTC14 s after it was requestedAdqYNMxc…

Commit

Commit 14

Program

Program 5round 0

Paid for by

agent-b.antibody.testnet our fixture agent B

Violationfees to treasury · high

receipt a1e3123df903…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.001 wNEAR bond, by our fixture agent B (agent-b.antibody.testnet). Nobody, the project included, can read it before its verdict.
6kx1dWvV…, NEAR transaction: 6kx1dWvVDxhxtPYQaJxKqx9VFpi4cyN2T6BtiYNsh7LT, opens an explorer in a new tab2026-11-0415:46:49 UTC · block 276,215,227
+40.8 s after the commit's block
Revealed · run 34 requested
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 64e23a21f487…, request sha256: 64e23a21f48723b89b724012d1d26e992ff1a246d2a716de1e2a220795b93bf7).

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 a1e3123df903…, receipt sha256: a1e3123df9034dc7d6e6bdda8ca933017af8abbdcf671088646aaafd817f4949. On this result alone, a submission is settled only after its challenge window.

Delivered in AdqYNMxc…, NEAR transaction: AdqYNMxc5hdqcGKaGndUAaRYS7w6HHVTTLd7kLnUgjAd, opens an explorer in a new tab

Check it yourself

antibody status --run 34

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

{
  "commit": 14,
  "id": 34,
  "mode": "verify",
  "outcome": {
    "Answered": {
      "at": 1793807264,
      "facts": {
        "extra": {
          "WrapD": {
            "wrap_d": "c58ac5de62809e0fa613b2a4bbf1e631e25ffd1efe07a80f481a8fe3342b8901124d2c45a71ca65f2d6df1bf58d45a981cecd5db10221c6926ec0df0"
          }
        },
        "impact_usd_micro": "1000000000",
        "keys": [
          {
            "slot": 1,
            "tag": "ae7e21c8af1b96023b13ae1daff4bcd1076b5b282e4f6ce6fb91e6fdae5f6de4"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "a1e3123df9034dc7d6e6bdda8ca933017af8abbdcf671088646aaafd817f4949"
      },
      "output_sha256": "c930f905588f7c3425d04cb057fbedbfa8e9d9755ff264790f33300baf8175b2",
      "tier": "T1"
    }
  },
  "payer": "agent-b.antibody.testnet",
  "program": 5,
  "request_sha256": "64e23a21f48723b89b724012d1d26e992ff1a246d2a716de1e2a220795b93bf7",
  "round": 0,
  "signer": "agent-b.antibody.testnet",
  "started_at": 1793807250
}

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

Check it yourself

tx AdqYNMxc5h… · NEAR archival RPC

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

outlayer-verify tx AdqYNMxc5hdqcGKaGndUAaRYS7w6HHVTTLd7kLnUgjAd

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

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 34

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