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

Run 106 · re-run · Violation · Attested on NEAR · Antibody

Run · re-run · program 12

Run 106

A re-run of commit 56's proof at round 1's code and rules: it still breaks 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

rerun

A re-run of a paid proof, a duplicate or a gap claim at a newer round's code and rules.

Kind

Violation

Keys

slot 1 (fees_to_treasury) · highae1a06842420…, tag of slot 1: ae1a0684242096f51ca736c04fbbd001ee2d89221806309c5010d21f72d88a9f

Impact

not published for a re-run

A re-run runs the project's fix against a proof it may not have paid for: its facts name only the keys that still break, never the impact or the harm.

Level

Attested on NEAR

Receipt sha256

13a4e92e34e42636…

Request sha256

348b5d84735fec47…

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

Output sha256

d8f57571e008ef08…

The SHA-256 of the facts near-antibody received: the TDX quote binds it.

Mode extras

none

Started

2026-11-08 17:20:02 UTCBTdYFSRA…

Answered

2026-11-08 17:20:14 UTC12 s after it was requestedBTdYFSRA…

Commit

Commit 56

Program

Program 12round 1

Paid for by

keeper.antibody.testnet our account

Violationfees to treasury · high

receipt 13a4e92e34e4…

Timeline

Every step is a NEAR transaction, timed by block from commit 56'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.
FesPHtSz…, NEAR transaction: FesPHtSzKdsh88To1qxE1YB2Lo3huDwYv1GhGGXDhB5N, opens an explorer in a new tab2026-11-0817:09:24 UTC · block 276,804,416
+10.6 min after the commit's block
Re-run requested at round 1's fix · run 106
At a proposed fix, the keeper re-runs every paid proof (the release gate holds only if all of them fail against it) and every duplicate and gap claim (the fix may promote them).
BTdYFSRA…, NEAR transaction: BTdYFSRA6bLqbXTmsJK8Tx1LxMsDvksM9vaRpFQ1K5PS, opens an explorer in a new tab

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

Delivered in BTdYFSRA…, NEAR transaction: BTdYFSRA6bLqbXTmsJK8Tx1LxMsDvksM9vaRpFQ1K5PS, opens an explorer in a new tab

Check it yourself

antibody status --run 106

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

{
  "commit": 56,
  "id": 106,
  "mode": "rerun",
  "outcome": {
    "Answered": {
      "at": 1794158414,
      "facts": {
        "extra": "None",
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 1,
            "tag": "ae1a0684242096f51ca736c04fbbd001ee2d89221806309c5010d21f72d88a9f"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "13a4e92e34e42636775f450767d7bb2337d68b7a194f11f7b7db6d7cd182405e"
      },
      "output_sha256": "d8f57571e008ef08a191c0d6336b7496f46c78cb5d2203658884230881b0726f",
      "tier": "T1"
    }
  },
  "payer": "keeper.antibody.testnet",
  "program": 12,
  "request_sha256": "348b5d84735fec47739f5334082ce23ab4cdad1d0f657477953244251399ab58",
  "round": 1,
  "signer": "keeper.antibody.testnet",
  "started_at": 1794158402
}

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. A re-run's result counts only once its run is attested on NEAR.

Attested in 97h99ec8…, NEAR transaction: 97h99ec8ReWZzroSfYf5UzJxiMiHbvjECsiWB5Dzmf7h, opens an explorer in a new tab

Check it yourself

tx BTdYFSRA6b… · NEAR archival RPC

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

outlayer-verify tx BTdYFSRA6bLqbXTmsJK8Tx1LxMsDvksM9vaRpFQ1K5PS

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

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 106

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