Skip to content

Conversation

gballet
Copy link
Collaborator

@gballet gballet commented Oct 7, 2025

Name: Thomas Coratger / @tcoratger
Team: EF ZKEVM
Start Date: 2024-12-01
Proposed weight: 1

Note

Although Thomas isn't in my team, I am making the application PR. I am acting with the approval of his team lead, @kevaundray. This proposal comes from an unusual direction, because I volunteered to step in after #400 left a few people exhausted.

Background

Before joining the Ethereum Foundation (EF), Thomas was a regular open-source contributor to key Ethereum infrastructure projects. For over a year, he made around 500 commits to Reth (an Ethereum execution client) and Alloy (a library for interacting with Ethereum), helping improve core tools used by the community.

He joined the EF's ARG team to focus on using ZK cryptography to help scale the main Ethereum layer and make it quantum-resistant. He later moved to the ZKEVM team upon its creation.

His first project at the EF was an exploration of binary fields using Hashcaster. The goal was to explore efficiency gains for cryptography in future versions of Ethereum.

Work Since March 2025

Plonky3 Development

Thomas is a core developer for Plonky3, a foundational library for building ZK systems. This work directly improves the security and performance of all projects that build on Plonky3.

zkEVM Book and General Research

To help others understand zkEVM field and how zkVMs can help scaling Ethereum, Thomas co-authored several sections of the zkEVM book. This is an educational resource that explains how ZK technology can scale Ethereum, making it more accessible to developers and researchers.

  • Book link: eth-act.github.io/zkevm-book/

He also conducts ongoing research on SNARKs and related topics like proximity proofs to explore ideas that enable future adoption of zk technology in the Ethereum protocol

@JustinDrake
Copy link
Contributor

Thomas is a machine, eg has hundreds of commits on https://github.com/tcoratger/whir-p3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants