Add Nixo#1
Closed
taxmeifyoucan wants to merge 1 commit into
Closed
Conversation
taxmeifyoucan
pushed a commit
that referenced
this pull request
Jan 12, 2026
**Proposal: Add zkEVM working group** This proposal outlines the rationale of creating a **zkEVM working group** within the Protocol Guild. This working group will maintain a focus on foundational protocol-level work that benefits the broader ecosystem, rather than specific product or client development. This PR acknowledges that Ethereum's ["snarkification" roadmap](https://blog.ethereum.org/2025/07/31/lean-ethereum) is still in its early stages and will likely evolve over several years. However, the launch of a zkEVM Attester Client is anticipated in the short-to-medium term: * [Shipping an L1 zkEVM \#1: Realtime Proving](https://blog.ethereum.org/2025/07/10/realtime-proving) * [Protocol Update 001 – Scale L1](https://blog.ethereum.org/2025/08/05/protocol-update-001) * [Making Sense of a ZK Staking Node](https://paragraph.com/@ethstaker/making-sense-of-a-zk-staking-node) Therefore, it is appropriate to include this initiative in Protocol Guild's "Wayfinding" category, which is defined as "the exploratory process to surface, describe and validate potential protocol changes". A similar longterm exploration would be post-quantum crypto, or the verkle/stateless efforts. This PR also adds Kev to this new category, who have already been engaging in this work. **Initial Eligible Scope** * Includes [prototyping work](sigp/lighthouse#7755) for a zkEVM attester client. The client will follow a [draft specification](https://github.com/ethereum/consensus-specs/pull/4591) that integrates both consensus and execution verification into a single binary. * May include guest program benchmarking, guest program security, zkEVM coordination, zkEVM proof verification, zkEVM specifications, and guest program compilation. **Exclusions** ["Lean Consensus" client teams](https://leanroadmap.org) are not covered by this proposal.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Name: Nixo (@nixorokish)
Team: Protocol Support
Start time: 2025-01
Weight: 1
Eligibility: Nixo has joined EF around a year ago and went full time in January. Currently, she is leading Protocol Support team which helps to facilitate processes around the core development. She has been contributing to running ACD, managing EthMag and helping to establish new tools like Forcast and ACDbot. Apart from helping with processes, she is also writing documentation and blogs with updates about core protocol. Her presence in the community goes far longer and the strong connection to validator community helps with our communication and feedback.
Some of her contributions: