Add 2026 projects #1
Conversation
codygunton
left a comment
codygunton
left a comment
There was a problem hiding this comment.
👋 EF ZKEVM team member here. I approve. I also make some suggestions regarding # Project 7: Security, where I'm part of the proposed working group.
jsign
left a comment
jsign
left a comment
There was a problem hiding this comment.
I'm Ignacio from EF ZKEVM team.
LGTM! Left some nit comments.
han0110
left a comment
han0110
left a comment
There was a problem hiding this comment.
I'm Han from EF ZKEVM team.
The planning LGTM!
|
Ben here from the Nimbus team. Looks good to me! |
maximmenshikov
left a comment
maximmenshikov
left a comment
There was a problem hiding this comment.
Approving from the view point of the part where I am mentioned.
@kevaundray please add me to security discussions too :)
Co-authored-by: Fredrik <fredrik@ethereum.org>
Co-authored-by: Justin Traglia <95511699+jtraglia@users.noreply.github.com>
projects.md
Outdated
| - Target specs | ||
| - SNARK prover | ||
| - SNARK verifier | ||
|
|
There was a problem hiding this comment.
if we add my suggestions above, then i guess we should also add milestones for that here
Co-authored-by: Justin Traglia <95511699+jtraglia@users.noreply.github.com>
Co-authored-by: Fredrik <fredrik@ethereum.org>
Co-authored-by: Justin Traglia <95511699+jtraglia@users.noreply.github.com>
Co-authored-by: Justin Traglia <95511699+jtraglia@users.noreply.github.com>
Co-authored-by: Justin Traglia <95511699+jtraglia@users.noreply.github.com>
Co-authored-by: Justin Traglia <95511699+jtraglia@users.noreply.github.com>
Co-authored-by: Justin Traglia <95511699+jtraglia@users.noreply.github.com>
Co-authored-by: Justin Traglia <95511699+jtraglia@users.noreply.github.com>
|
I am Uche from EPF. The planning looks good to me! |
jflo
left a comment
jflo
left a comment
There was a problem hiding this comment.
Besu team approves with some notes on personnel changes.
| - zkVM that follows the security guidelines and proof sizes in EF cryptography research blogpost [TODO: INSERT LINK WHEN PUBLISHED] | ||
| - This will have provable security as a requirement | ||
| - Create Fork readiness review document | ||
| - This includes decisions on whether we will need bug bounties and audits for optional proofs |
There was a problem hiding this comment.
Not my call here, but I think this should be done to establish and evaluate a standard for zkVMs as these are new artefacts.
kevaundray
force-pushed
the
kw/add-project
branch
from
eb6abad to
b28d05b
Compare
Co-Authored-By: Alexander Hicks <alexanderlhicks@users.noreply.github.com> Co-Authored-By: raulk <raulk@users.noreply.github.com>
kevaundray
force-pushed
the
kw/add-project
branch
from
b28d05b to
417d11d
Compare
jonathanpwang
left a comment
jonathanpwang
left a comment
There was a problem hiding this comment.
I'm Jonathan from the Axiom team (maintainers of OpenVM zkVM).
I left some questions around where ExecutionWitness optimizations that fall in-between the EL client and Guest Program should be categoried.
Co-authored-by: Jonathan Wang <jonathanpwang@users.noreply.github.com>
|
|
||
| ## Project 6: Benchmarking and Metrics | ||
|
|
||
| This a perpetual project. |
20 participants
Original: https://hackmd.io/@kevaundray/SkxCvcQMZe
Note:
Working group does not imply that you are bounded to any commitment. The working group for a particular project consists mainly of the people already working on that project, are responsible for that project within their respective team or their input will be needed for important parts of the project
List of teams that we have reached out to and have replied:
EL
CL
EF