A visitor's practice try's sealed proof broke the “vault keeps its ether” rule (low). Run in the enclave, attested on NEAR and paid 0.001 wNEAR instantly, under the instant cap, 29.2 s after its commit.
PaidLowZero-knowledge proofpractice
Program
Program 13Practice 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 b4f3bc08a054…, request sha256: b4f3bc08a054d9acc04ae64cd2a3a0d77d0cab0bbbfb6d6c46e5811bd0abab9c). 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 d0f93a4eae60…, receipt sha256: d0f93a4eae6002661d462340158f12874fdfbf762cac321fee9d822b5f98da3d. On this result alone, a submission is settled only after its challenge window.
Instant payout: attested on NEAR, under the instant cap and within its window's instant budget. Credited to the practice vending contract (practice.antibody.testnet).
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.
Holds if: the run is attested: its quote was verified on NEAR
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.
d0f93a4eae60…, the proof's receipt sha256: d0f93a4eae6002661d462340158f12874fdfbf762cac321fee9d822b5f98da3d
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.