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 5cce5352a1f0…, request sha256: 5cce5352a1f0bea1ab236a714bb46b6d225691f13039b280a4ef2e57eb25cc54). 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. Its run's facts carry no disclosure wrap, so no disclosure key opens it on chain.
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: No violation, receipt d4552aa7bce3…, receipt sha256: d4552aa7bce3f97ebe335ed253aac9fb58f2bee3b626f6aa897e2f85831e7353. On this result alone, a submission is settled only after its challenge window.
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.
d4552aa7bce3…, the proof's receipt sha256: d4552aa7bce3f97ebe335ed253aac9fb58f2bee3b626f6aa897e2f85831e7353
equals the enclave's
Kind
NoViolation
equals the enclave's
Slots (severity)
none
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.