THE LEDGER

ZK Tech

40 RESULTS · PAGE 1 OF 4 · ONE LINE PER STORY, NUMBERED

PAGE 1
N°0486ZK TechRISC Zero zkVM 3.1.0 fixes Groth16 claim forgery and four other flawsrisc0-zkvm 3.1.0 fixes five proof-system bugs, including one that let a single valid Groth16 receipt be reused to forge any claim. Upgrade the toolchain, regenerate all receipts and verify through the new 0xe71e6620 verifier.—5 MINN°0477ZK TechOpenVM v2.1.0 adds certified STARK verifier, fixes 5 advisoriesOpenVM v2.1.0 adds optional STARK proof verification with a Lean-certified Swirl verifier and patches five advisories, two rated High. Upgrade from 1.x or 2.0.x, rebuild your guests and check any custom algebra types.—4 MINN°0469ZK TechEthereum consensus P2P inventory maps post-quantum ENR and TLS changesAn Ethereum Research post from Nyx Foundation lists the consensus-layer networking keys that need post-quantum replacements. Client and libp2p teams should audit secp256k1 uses and ENR size limits now.—5 MINN°0465ZK TechSP1 v6.10.0 moves the SDK to Tonic 0.14.6 and fixes x86 JIT remwSP1 v6.10.0 upgrades sp1-sdk to Tonic 0.14.6 and Prost 0.14, a breaking change for code that passes Tonic types. It also fixes a native x86-64 remw bug and a cluster shard-redelivery failure. Align your Tonic version before you upgrade.—5 MINN°0459ZK TechML-DSA, SLH-DSA and STARKs: what replaces ECDSA, BLS and KZGFind every ECDSA, Schnorr, BLS, KZG and pairing-SNARK use in your stack now. Then plan for ML-DSA, SLH-DSA or XMSS signatures that are tens to hundreds of times larger, and for the NIST 2030/2035 and Ethereum ~2029 targets.—8 MINN°0455ZK TechSP1 vs RISC Zero vs Jolt vs OpenVM: choosing a zkVM in 2026Compare SP1 v6.9.0, RISC Zero 3.0, Jolt (alpha) and OpenVM v2.0.2 on guest languages, proof system, post-quantum status, where proving runs and license. Then run each project's documented minimal flow before you pick one.—7 MINN°0452ZK TechLongfellow ZK: how zero-knowledge age checks work on mdoc IDsLongfellow ZK lets a wallet prove an mdoc attribute such as age_over_18 without sending the issuer signature or other data. Pin the circuit hash, use fresh nonces, keep an IACA trust list, and plan for plain-mdoc fallback.—9 MINN°0447ZK TechSP1 v6.9.0 adds authentication for standalone clientsSP1 v6.9.0 lets standalone network clients configure authentication and includes GPU, zkEVM library, and CLI fixes. Review the release and update your SDK or toolchain pins if they apply to your setup.—3 MINN°0438ZK TechJolt zkVM Bytecode Expansion Gets Lean Formal VerificationLayerZero Research has formally verified the bytecode-expansion layer of the Jolt zkVM in Lean, turning a critical translation step from a testing problem into a machine-checked equivalence claim. The milestone is valuable—but deliberately narrower than a full zkVM security proof.—2 MINN°0431ZK TechzkAPI Separates API Billing From Identity With ZK ProofsThe Ethereum Foundation and Open Anonymity Project have released zkAPI, an experimental system that separates API payment from user identity with zero-knowledge proofs. Its most useful lesson for ICP developers is architectural: privacy can be applied to metered authorization and settlement without redesigning the API being consumed.—2 MINN°0427ZK TechzkTLS Proof of Protocol Execution: What ICP Developers Should KnowA new zkTLS preprint proposes proving that a claimed response came from a real protocol execution—not merely that someone knows an input-response pair. That distinction matters for developers bringing authenticated web data into ICP applications.—2 MINN°0420ZK TechLongfellow ZK IETF Adoption Call: What ICP Builders Should KnowA September revision of Google’s Longfellow ZK proposal is now under a CFRG adoption call. Its practical lesson for ICP builders is to isolate proof formats and pin versions while the protocol is still moving.—2 MIN