Our rehearsal's sealed proof broke the “vault keeps its ether” rule (low). Run in the enclave and paid 0.001 wNEAR after its challenge window, 83.3 s after its commit.
PaidLowZero-knowledge proofpractice
Program
Program 10Practice program — a tutorial (testnet)practice
On the practice program: our deliberately vulnerable tutorial, open to anyone with no account. Its payouts are testnet wNEAR, with no value. Try it yourself
The sealed proof went to the enclave, in a request near-antibody built from its own records (request sha256 cbbfb5e0c42e…, request sha256: cbbfb5e0c42e74b4cf453af5173a310a6d9eac956ed0160a5e99bf098d266b1e). The run was paid for by the practice vending contract (practice.antibody.testnet).
antibody try and this site seal a practice try under a public content key, so anyone can open it; a try sealed another way, or before that key existed, used a random one. The check below tells which. After payment, the project reads it through its release wrap; it opens to everyone at disclosure, one key per tag and round.
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 8bf64b138bd7…, receipt sha256: 8bf64b138bd7839d74909e98977fa5b199f08150c53c4fd5c0acbc43325c09b5. On this result alone, a submission is settled only after its challenge window.
Not attested on NEAR: the verdict stands on the enclave's result and its challenge window. Our attestation relayer sends each answered run's quote, and anyone may.
Holds if: the run's answer is the enclave's result, not attested
Zero-knowledge proofconfirmed on NEAR
A zero-knowledge proof of the verdict
near-t2 verified an SP1 proof that the verifier, re-run on the enclave's exact input, gives the enclave's receipt, kind and rules, and compared every bound value with near-antibody's records. It claims no privacy (anyone can open the proof it re-runs: disclosed, or under a published or public content key), and no payout depends on it.
8bf64b138bd7…, the proof's receipt sha256: 8bf64b138bd7839d74909e98977fa5b199f08150c53c4fd5c0acbc43325c09b5
equals the enclave's
Kind
Violation
equals the enclave's
Slots (severity)
0 low
equals the enclave's
A different request, run, blob, base, manifest, anchor, program, verifier or severity is rejected outright; a different receipt, kind or slots is recorded as a contradiction.