Excited to share that /eas was awarded a research grant from the @ethereumfndn to bring ZK + attestations closer together!

Want in? Reach out if you are:
⤷ Passionate about zk + attested data
⤷ A builder looking to make zk attestations
⤷ A zk provider helping builders build

The Ethereum Foundation (EF) is a non-profit that supports Ethereum. Learn more at ethereum.foundation.

Core team @ Ethereum Attestation Service. Product person with some salty dev & design skills. 

https://attest.org

Chat: https://warpcast.com/~/channel/eas

Our path forward is to:
⤷ Collaborate with ZK and attestation providers in a credibly neutral way
⤷ Map existing ZK + attestation solutions and priority use cases
⤷ Identify limitations and opportunities in generating ZK proofs from attestations
⤷ Explore how zkVMs can enhance privacy and scalability in attestation-based experiences
⤷ Expand interoperability by including other signed data like JWT tokens.

ZK attestation use cases we want to enable:
⤷ Privacy-preserving proofs for identity, funds, employment, and attendance.
⤷ ZK voting, ticketing, and reputation systems
⤷ ZK marketplaces and land registries
⤷ ZK attestations and their role with autonomous agents
⤷ Bringing signed data from web2 into Ethereum using attestations as an oracle service

Expected outcomes:
⤷ Clear understanding of how ZK and attestations can work together.
⤷ Defined paths and best practices for generating ZK proofs from arbitrary attestations.
⤷ Interoperability guidelines that recommend compatibility between different zk systems and attestation methods
⤷ Roadmap for dev tooling and collaboration opportunities.
⤷ Short-term use cases to focus on.

Sample questions we're after:
⤷ Best practices for generating zkps from off/onchain attestations
⤷ Near-term vs. long-term impact for builders
⤷ Risks and limitations in proof generation
⤷ How zkVMs change efficiency, security, and privacy
⤷ Where attestations fit after a ZK proof is generated