Commit · program 13 · round 0
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
Bond
0.0001 wNEAR
A duplicate is never paid, and its bond is returned.
Payout
0 wNEAR
0.001 wNEAR stays reserved: if a later round's fix stops the earlier claim but not this proof, it proves a distinct bug and is promoted, paid at its original priority.
A duplicate is never paid
By a visitor's practice try (v061resume.practice.antibody.testnet), committed (31.0 min before this one). Commit order is priority: the first proof of a key is the one paid.
Committed
Revealed · run 161 requested
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. A duplicate is never wrapped for the project; at disclosure it opens with the claim it duplicates.
OutLayer's operator delivered the enclave's output to near-antibody: Violation, receipt 4289a52656af…, receipt sha256: 4289a52656afe36e3ddb8c01c776f00325274db40a0e15f6036b9a940913390b. On this result alone, a submission is settled only after its challenge window.
Delivered in 3RuHSJHo…, NEAR transaction: 3RuHSJHoXSiRGvXBCfWAk7ZbNoVQ9PKYrCCsHtxyJJbN, opens an explorer in a new tab
antibody status --run ef4d2b7b7a153bf30ed4a02f46be81385eab5ce7de343b80e083310186f1dd63ef4d2b7b7a153bf30ed4a02f46be81385eab5ce7de343b80e083310186f1dd63A tag is a keyed hash of the rule and the entry point, under the program's key, which only the enclave holds.
The earlier claim's proof
This proof
Kept as a proof record: its keys, its receipt and its transactions. At disclosure it opens with the claim it duplicates.
Holds if: this commit's run 161 records tag ef4d2b7b7a15…
Holds if: the earlier claim's run 159 records the same tag
Holds if: state Duplicate, of commit 69
antibody status --commit 71Enclave verdict: violation of the “vault keeps its ether” rule
Attested on NEAR
Duplicate of commit 69
T2 confirmed
The next round (not yet)
Disclosure (not yet)
antibody program read --api fetches.Holds if: near-antibody stores commitment 974696979bc7… for commit 71
Key: sha256("antibody/practice/public-content-key/v1|bounty.antibody.testnet/13|capdemo.antibody.testnet")
The state and the payout are checked under What it settled; the run's TDX quote (antibody tee check, outlayer-verify) under How the verdict is checked.
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.
Attested in H75ojrEE…, NEAR transaction: H75ojrEE1QLg4DJxbDq4KiYW7nqvanJUJQc8n13YRmGM, opens an explorer in a new tab
antibody tee check --request-id <the run's OutLayer request>outlayer-verify tx 3RuHSJHoXSiRGvXBCfWAk7ZbNoVQ9PKYrCCsHtxyJJbNHolds if: the run is attested: its quote was verified on NEAR
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.
Recorded on NEAR in GoR4jNcY…, NEAR transaction: GoR4jNcYmuZuR7WbR2SxZdtZC2jHBzPN1uTor5iwTD28, opens an explorer in a new tab
What its public values bind
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.
antibody zk status --run 161Holds if: near-t2's record says confirmed
9 of 22 commits. Every commit of program 13