Repository navigation
zk-proofs: UltraHonk verifier now needs Protocol 28+, not 26+聽#159
Description
馃 Automated message from the Stellar Triage Bot.
The zk-proofs Noir walkthrough says the rs-soroban-ultrahonk verifier needs Protocol 26+. That is the CAP-0080 host-function floor. The current verifier release needs more. Copilot raised this on #158; it is outside that PR's scope.
Facts (checked 2026-10-21):
- The verifier README targets
soroban-sdk28.x. It says contracts built with it require Protocol 28 or newer. - crates.io
ultrahonk_soroban_verifier0.1.0 (2026-10-12) depends onsoroban-sdk ^28.0.0. - Mainnet and Testnet run Protocol 29, so no live deploy breaks today.
Places to update in skills/zk-proofs/SKILL.md:
- Line 12: "Last verified against Protocol 27".
- Lines 39, 45, 163, 165, 183: the "Protocol 26+" requirement for this verifier.
evals/scenarios/zk-proofs/02-noir-onchain.json: the "needs Protocol 26+" assertion.
Also worth a check in the same pass:
- The README pins proof tooling to Nargo 1.0.0-beta.9 + Barretenberg 0.87.0 with the Keccak oracle. The walkthrough's
bb prove/bb verifylines name no oracle and nobb write_vkstep. - The README now reports an OpenZeppelin audit (report dated 2026-09-18). Line 165 still says "check its audit status".
Activity
stellar-triage-bot commentedon Oct 21, 2026
馃 Automated message from the Stellar Triage Bot.
Picked this up. I am checking whether I can ship an airtight fix.
stellar-triage-bot commentedon Oct 21, 2026
馃 Automated message from the Stellar Triage Bot.
I opened #160 with the fix. It sets the verifier floor to Protocol 28+, pins the proof tooling, and updates the eval.
stellar-triage-bot commentedon Oct 21, 2026
馃 Automated message from the Stellar Triage Bot.
Fixed in #160, now merged. The Noir walkthrough now says Protocol 28+ for the current verifier release. It also pins Nargo 1.0.0-beta.9 + bb 0.87.0 with the Keccak oracle and names the OpenZeppelin audit. The eval scenario matches.