Plonk, STARK, and Halo2 would remain unsupported.

These verifiers must be maintained to remain compatible with both the proving systems (e.g., Groth16, PLONK...

Similarly, SP1 (Succinct’s zkVM) explicitly exposes proof type tradeoffs (core, compressed, PLONK) because...zkVerify supports a broad array of proof systems (Groth16, Fflonk, UltraPlonk/UltraHonk, Risc0, SP1, Plonky2...

...that different zk applications use various types of proofs, such as Groth16, Halo2-KZG, STARK, and Plonk...

...optimistic rollup camp say about zero knowledge proofs (ZKPs) Too new and therefore risky, with STARKs and PLONKs...

...on Ethereum today are recommended to use proof systems that utilize KZG commitments (such as various Plonk-based...

Proof System selectionWhen it comes to proof systems for Bitcoin, pairing-based systems like Groth16, Plonk...

Precompiles are designed for specific purposes, such as for a particular proving system like Groth16 or Plonk...The movement began with Plonky2 introducing 64-bit fields, followed by systems like Baby Bear and M31...This breakthrough is going to be used in Stwo prover by Starkware and integrated into Plonky3.

In fact, many of the proving systems Celestia plans to use (like Halo or Plonky2) won’t even implement...

For their ZK-IBC construction, Polymer Labs has selected a combination of the recursive Plonky2 and Groth16...

Specifically, after committing $1B to zk-rollups last year, the company continued to advance its zkEVM & Plonky2...

In particular, they continue to advance their zkEVM and Plonky2 offerings after committing $1B to zk-rollups...

In particular, they continue to advance their zkEVM and Plonky2 offerings after committing $1B to zk-rollups...

...system. zkVerify supports all major proof types: Groth16, Ultraplonk, Ultrahonk, SP1, Fflonk, Risc0, Plonky2...