Dynamic Groth16 Image IDs Land In Rusty Kaspa

The ZK script path got one concrete post-Toccata upgrade in early August: rusty-kaspa gained a dynamic-image-id Groth16 verifier fragment.

Ori Newman opened and later merged PR #1067, titled around append_r0_groth16_verifier_dynamic_image_id, with a companion append_r0_groth16_verifier path that does not take an image id in the same way. GitHub records the merge at 2026-08-02T10:25:51Z. (PR #1067)

The R&D channel discussion started earlier. On July 5, Sutton asked whether the pre-stack contract for the dynamic path should be [..., journal_hash, image_id, compressed_proof] rather than the reverse image-id ordering under discussion, calling it a nit and noting it would move the first swap from the dynamic helper into the base helper. He later said the change was approved from his side. ^{[1] [2] [3] [4]}

By July 8 the remaining request was API completeness. saefstroem asked for a corresponding WASM method, noting that the other fragments already expose an API through ZkScriptBuilder. Newman agreed and asked him to leave it as review feedback. saefstroem did, saying he would approve once that landed. ^{[5] [6] [7] [8] [9]}

The practical meaning is straightforward. Earlier ZK SDK work made it easier to build RISC Zero and Groth16 verifier scripts without hand-writing every opcode path. The dynamic image-id helper extends that surface so the image id is not frozen into one static verifier shape. That matters for flows where the proof family stays Groth16 but the guest image identity can change across releases or application variants. (PR #1067) (PR #953)

Silverscript moved on the same axis days later. On August 7, Newman merged elldeeone's g16.verify builtin, giving Silverscript a direct low-level call into the Groth16 precompile path. That does not replace the rusty-kaspa fragment work. It gives the higher-level language a matching verb once the node-side verifier surface exists. ^[10] (PR #138)

Keep the claim tight. This is not a proof that production apps should rely on arbitrary dynamic image switching tomorrow. It is a merged script-building capability: dynamic Groth16 image ids in rusty-kaspa, review pressure for WASM parity, and a Silverscript builtin that can target the same verifier family.

All sources link to public messages in the Kaspa Core R&D (public) Telegram channel.