-
Notifications
You must be signed in to change notification settings - Fork 142
Add zkEVM working group #400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 3 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -2,7 +2,7 @@ | |||||
|
|
||||||
| ## 1.1 Active Working Groups + Members | ||||||
|
|
||||||
| Individuals from active working groups produce the membership by opting into Protocol Guild. The delineation between categories and working groups below is for informational purposes only - contributors quite often collaborate across many different working groups and projects. The four categories include: | ||||||
| Individuals from active working groups produce the membership by opting into Protocol Guild. The delineation between categories and working groups below is for informational purposes only - contributors quite often collaborate across many different working groups and projects. Working groups should undergo periodic reviews as the core protocol development roadmap evolves. The four categories include: | ||||||
|
|
||||||
| - Wayfinding | ||||||
| - Governance | ||||||
|
|
@@ -14,6 +14,13 @@ Individuals from active working groups produce the membership by opting into Pro | |||||
| - 11 Working Groups, 36 contributors | ||||||
| - Venue: breakout calls | ||||||
| - Artifacts: Research & POCs | ||||||
| - Research Constraints | ||||||
| - Generally agreed to be a significant and worthwhile direction for the protocol | ||||||
| - Composed of contributors who are sufficiently tethered to Ethereum's core protocol R&D, potentially being part of existing entities or teams focused on such work | ||||||
| - Performed according to general research principles, including open production of artifacts, peer review, and systematic, documented efforts to compare different approaches | ||||||
| - Prototyping / "Research Engineering" Constraints | ||||||
| - Supporting a research direction that satisfies the criteria outlined above | ||||||
| - Equipped with sufficient resources that are commensurate with the complexity and confidence of the research direction, necessary to move the research direction to a concrete proposal for mainnet | ||||||
|
|
||||||
| |**Architecture & Coordination** (5 contributors) |**Weight** |**Other contributions** | | ||||||
| |:---|:---|:---| | ||||||
|
|
@@ -36,8 +43,7 @@ Individuals from active working groups produce the membership by opting into Pro | |||||
| | **Data Availability** (2 contributors) | | | | ||||||
| | [Dmitriy Ryajov](https://github.com/dryajov/) | 0.5 | Codex DAS (IFT) | | ||||||
| | [Leonardo Bautista-Gomez](https://github.com/leobago/) | 0.5 | [ethresear.ch/u/leobago](https://ethresear.ch/u/leobago/) | | ||||||
| | **Execution (Gas limit, EVM, delayed, History Expiry)** (1 contributors) | | | | ||||||
| | [Radosław Zagórowicz](https://github.com/rodiazet) | 1 | [ethereum/evmc](https://github.com/ethereum/evmc/pulls?q=author%3Arodiazet), [ethereum/evmone](https://github.com/ethereum/evmone/pulls?q=author%3Arodiazet), [ethereum/tests](https://github.com/ethereum/tests/pulls?q=is%3Apr+author%3Arodiazet), [ipsilon/eof](https://github.com/ipsilon/eof/pulls?q=author%3Arodiazet) | | ||||||
| | **Execution (Gas limit, EVM, delayed, History Expiry)** (0 contributors) | | | | ||||||
| | **Portal** (1 contributor)| | | | ||||||
| | [Piper Merriam](https://github.com/ethereum/portal-network-specs) | 1 | | | ||||||
| | **Networking** (2 contributor) | | | | ||||||
|
|
@@ -56,14 +62,15 @@ Individuals from active working groups produce the membership by opting into Pro | |||||
| | [Milos Stankovic](https://github.com/morph-dev) | 1 | [morph-dev/pglanding-morph-dev](https://github.com/morph-dev/pglanding-morph-dev) | | ||||||
| | [Toni Wahrstätter](https://github.com/nerolation) | 1 | [nerolation/pglanding-nerolation](https://github.com/nerolation/pglanding-nerolation) | | ||||||
| | [Rahul](https://github.com/raxhvl) | 1 | [raxhvl/pglanding-raxhvl](https://github.com/raxhvl/pglanding-raxhvl) | | ||||||
| | **Statelessness** (2 contributors) | | | | ||||||
| | **Statelessness** (1 contributors) | | | | ||||||
|
||||||
| | **Statelessness** (1 contributors) | | | | |
| | **Statelessness** (2 contributors) | | | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is because it's going to clash with another PR I'm preparing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can't your PR or this PR rebase depending on which one gets in first?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I find this constraint to be too broad to effectively constrain. "Generally", "Significant" and "Worthwhile" are all words that lack precision, and thus forfeit enforcement of Ethereum values. Protocol Guild subsidized research should be required to be value aligned with Ethereum.
For example, in this current example, I agree that the zkEVM working group is "significant and worthwhile", but the centralization threat of provers remains an ignored design space. If an area of research is willing to sacrifice decentralization in favor of scaling, that is a SIGNIFICANT departure from Ethereum values, which would sail right through these constraints.
We need to try harder to protect what we value.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also don't think we should be changing category constraints while at the same time trying to add a working group. Feels like we're changing the rules to support the proposal instead of changing the rules to support the consensus view of the guild.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
appreciate the feedback, your consistent disapproval on grounds of "insufficient decentralization" is noted 🫡
one counterpoint to consider - the original "Casper the Friendly Finality Gadget" (FFG) design required 1500 ETH requirements and would have likely been excluded from funding had 1. PG existed 2. used your suggested requirements at the time. this work was important to inform the 32 ETH design of the beacon chain the community settled on.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great example! In that case I still would have excluded that research from Protocol Guild, till they got the design to a more decentralized one. Once that was proved, I would admit the working group, and backdate their working weights to the time of group inception.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also eth was <$10 when the original idea of 1500 requirement was being proposed, so not sure you should view it in the context of today's price.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jflo tangent but I think it's quite untrue to claim that the threat of provers is an ignored design space. It's precisely because it's not ignored that I am personally quite confident in adding zkEVM as a WG, it meets the criteria of "systematic and documented efforts to arrive at a result comparing with different approaches".
While I estimate the chances of changing our minds on this are low, it would be perfectly possible for new results to show that indeed provers are a threat and the approach is non-viable. Falsifiability is a necessary condition to consider the effort rigorous.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure that's correct?
under the period of FFG consideration (using my rough cutoffs), the cost of a single validator would have ranged from $450,000 to $2,175,000
it's easy to look back with hindsight and say "this was unacceptable", when this is was the tradeoff space core devs found themselves designing in. We will likely do the same in 5 years if the limit is lower than 32 ETH 🤞