Proposal: add Snarkification working group

[tvanepps]

Proposal: add Snarkification working group

Context: The potential integration of zero-knowledge proofs (ZKPs) in the Ethereum protocol presents a critical need for focused, collaborative work to ensure their security, interoperability, and responsible development. This includes the advent and proliferation of zkVMs, zkEVMs, and the appearance of "real-time proving" on our horizon.

This proposal outlines the establishment of a "Snarkification" working group within the Protocol Guild to address these evolving needs.

Mission: The Snarkification working group will support research, security, standardization, formal verification, and implementation efforts related to the integration of ZKPs into core Ethereum protocols.

This PR also recategorizes existing PG members (Kev, Carl, rodiazet, Ignacio) who have already been engaging in this work.

Scope and Subcategories

The Snarkification working group will initially focus on two critical subcategories:

1. Execution (zkEVMs): This subcategory will focus on the use of zkVMs to prove the Ethereum L1 blocks. This includes:

• R&D for design, security, efficiency
• Formal verification
• Standardization efforts for zkEVM architectures and proof formats to promote interoperability

2. Consensus (Lean, Beam):

• Research into using ZKPs for state transition function (STF) verification (e.g., in projects like the Beam chain)
• Investigation of ZKP applications for signature aggregation and other consensus-critical operations

Eligibility and Exclusion

Membership within the Snarkification Protocol Guild Working Group is intended to foster collaborative efforts at the protocol level. PG support of beam chain R&D through the Snarkification WG does not currently extend to beam client teams—a separate proposal and framework of requirements would be necessary. Similarly, if there is a need for a spec-specific working group (ie. similar to EELS for the execution layer), this can also be added in the future.

Production zkVM teams are expected to stay outside of the scope of PG for the foreseeable future. The intention is to maintain a focus on foundational protocol-level work that benefits the broader ecosystem, rather than specific product or client development.

[JustinDrake]

Makes sense to me! :) I love seeing snarkification steadily seeping into L1 R&D. Also exciting to see what may be PG's first explicitly mention of Lean/Beam efforts.

[lightclient]

Majority of current work I am aware of is for out-of-protocol zk systems, like succinct. I don't see a difference between this and MEV boost. The protocol does not require them to operate. We are at least 3-5 years away from seriously considering a protocol change relating to zk.

I think it is too early to consider this work for PG. It would make sense to revisit when a zk protocol is in consideration as a headlining feature on L1.

[tvanepps]

for future commenters, let's direct the discussion to the PG discord, where it is already taking place and to avoid bifurcating