Problem
skills/zk-proofs/SKILL.md still describes the pre-X-Ray world:
| BN254 host functions | CAP-0074 | Proposed — check current status |
| Poseidon/Poseidon2 hash | CAP-0075 | Proposed — check current status |
| Noir + Barretenberg | UltraHonk | BN254 | Not yet — attest off-chain verification |
"…neither the proof system nor the curve is on-chain verifiable on Stellar today."
Current reality
- CAP-0074 (BN254 host functions) and CAP-0075 (Poseidon/Poseidon2) shipped in Protocol 25 "X-Ray" (mainnet January 22, 2026).
- UltraHonk proofs over BN254 verify on-chain today via Nethermind's rs-soroban-ultrahonk — this is what OpenZeppelin's Confidential Tokens developer preview runs on (testnet).
Why it matters
The skill is explicitly "status-sensitive" and consumed by AI agents (e.g. via the stellar-dev plugin and the Stellar Raven gateway). As written, it tells builders that on-chain UltraHonk/BN254 verification is impossible — steering them away from the exact capability the Confidential Tokens preview and recent ZK hackathon scope are built on. The "always verify CAP status" guardrail helps, but the hardcoded "Not yet" rows read as conclusions, not prompts to check.
Suggested fix
- Status table: CAP-0074 and CAP-0075 → "Available (Protocol 25+)"
- Toolchain table: Noir + Barretenberg / UltraHonk / BN254 → "✅ via CAP-0074 host functions (Protocol 25+)"; same for the other BN254-gated rows (Circom default, RISC Zero Groth16 wrap)
- Remove/rewrite the "neither the proof system nor the curve is on-chain verifiable" walkthrough framing, and the "(BN254 proposal)" / "(Poseidon proposal)" link labels
- Optionally add a "last verified against Protocol X" line at the top, so future staleness is self-documenting
Problem
skills/zk-proofs/SKILL.md still describes the pre-X-Ray world:
| BN254 host functions | CAP-0074 | Proposed — check current status |
| Poseidon/Poseidon2 hash | CAP-0075 | Proposed — check current status |
| Noir + Barretenberg | UltraHonk | BN254 | Not yet — attest off-chain verification |
"…neither the proof system nor the curve is on-chain verifiable on Stellar today."
Current reality
Why it matters
The skill is explicitly "status-sensitive" and consumed by AI agents (e.g. via the stellar-dev plugin and the Stellar Raven gateway). As written, it tells builders that on-chain UltraHonk/BN254 verification is impossible — steering them away from the exact capability the Confidential Tokens preview and recent ZK hackathon scope are built on. The "always verify CAP status" guardrail helps, but the hardcoded "Not yet" rows read as conclusions, not prompts to check.
Suggested fix