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

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

Run · re-run · program 5

Run 45

A re-run of commit 18's proof at round 1's code and rules: it still breaks the solvency 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 0 (solvency) · criticala74dddb61406…, tag of slot 0: a74dddb61406f343a53af7298ef64be2f9334763dfcd23f17ca3b85547e53b8c

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

43bd3ea0ce4b5063…

Request sha256

57db40473062d3ab…

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

Output sha256

26172f7ebe5658b0…

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

Mode extras

none

Started

2026-11-04 15:57:28 UTC8Z2Rreht…

Answered

2026-11-04 15:57:45 UTC17 s after it was requested8Z2Rreht…

Commit

Commit 18

Program

Program 5round 1

Paid for by

keeper.antibody.testnet our account

Violationsolvency · critical

receipt 43bd3ea0ce4b…

Timeline

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

0.0 s (the commit's block)
Committed
A sealed proof and a 0.001 wNEAR bond, by our fixture agent F (agent-f.antibody.testnet). Nobody, the project included, can read it before its verdict.
5q7s1wJW…, NEAR transaction: 5q7s1wJWzpazCW6wmtk13RS5ZZHDNakQSBXKyhYxjdYL, opens an explorer in a new tab2026-11-0415:49:03 UTC · block 276,215,459
+8.4 min after the commit's block
Re-run requested at round 1's fix · run 45
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).
8Z2Rreht…, NEAR transaction: 8Z2RrehtFTD7vAT2hEpEHvgcmLoyanbTQ2xBQixHtjMN, 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 43bd3ea0ce4b…, receipt sha256: 43bd3ea0ce4b5063ec5a7ff479e324d1a87ffb6e7ee84eca27e82154d518e1cf. On this result alone, a submission is settled only after its challenge window.

Delivered in 8Z2Rreht…, NEAR transaction: 8Z2RrehtFTD7vAT2hEpEHvgcmLoyanbTQ2xBQixHtjMN, opens an explorer in a new tab

Check it yourself

antibody status --run 45

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

{
  "commit": 18,
  "id": 45,
  "mode": "rerun",
  "outcome": {
    "Answered": {
      "at": 1793807865,
      "facts": {
        "extra": "None",
        "impact_usd_micro": "0",
        "keys": [
          {
            "slot": 0,
            "tag": "a74dddb61406f343a53af7298ef64be2f9334763dfcd23f17ca3b85547e53b8c"
          }
        ],
        "kind": "Violation",
        "protected_harm_usd_micro": "0",
        "reason": null,
        "receipt_sha256": "43bd3ea0ce4b5063ec5a7ff479e324d1a87ffb6e7ee84eca27e82154d518e1cf"
      },
      "output_sha256": "26172f7ebe5658b0ed703ebb0cdd3478ac9c65a25c0ed47a7b8b0bf13c82d30b",
      "tier": "T1"
    }
  },
  "payer": "keeper.antibody.testnet",
  "program": 5,
  "request_sha256": "57db40473062d3abb50cfa37785a2fdcbdee7fa6fc7181cacee0fd5817104569",
  "round": 1,
  "signer": "keeper.antibody.testnet",
  "started_at": 1793807848
}

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

Check it yourself

tx 8Z2RrehtFT… · NEAR archival RPC

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

outlayer-verify tx 8Z2RrehtFTD7vAT2hEpEHvgcmLoyanbTQ2xBQixHtjMN

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

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 45

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