[Draft] Add a maximum cap per project #325
There are no files selected for viewing
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -9,14 +9,14 @@ Protocol Guild eligible projects must: | |
|
|
||
| Eligible projects must also target at least one of the following projects/areas related to Ethereum core protocol upgrades, maintenance and development: | ||
|
|
||
| | Description | Repos/Projects | Current Members / Max Cap | | ||
| |:--|:---|:---| | ||
| | Work on the canonical protocol specs. <br/> Should be implementation agnostic + unopinionated | - [Consensus specs](https://github.com/ethereum/consensus-specs) <br/> - [Execution specs (EELS)](https://github.com/ethereum/execution-specs) <br/> - [Execution APIs](https://github.com/ethereum/execution-apis) | 3 / 5 | | ||
| | Ethereum mainnet client implementations. <br/> Must be well-tested, technically differentiated, <br/> and production ready | - [Erigon](https://github.com/erigontech/erigon) <br/> - [EthereumJS](https://github.com/ethereumjs) <br/> - [Geth](https://github.com/ethereum/go-ethereum) <br/> - [Grandine](https://github.com/grandinetech/grandine) <br/> - [Hyperledger Besu](https://github.com/hyperledger/besu) <br/> - [Lighthouse](https://github.com/sigp/lighthouse) <br/> - [Lodestar](https://github.com/ChainSafe/lodestar) <br/> - [Nethermind](https://github.com/NethermindEth/nethermind) <br/> - [Nimbus](https://github.com/status-im/nimbus-eth2) <br/> - [Prysm](https://github.com/prysmaticlabs/prysm) <br/> - [Teku](https://github.com/ConsenSys/teku) <br/> - [Reth](https://github.com/paradigmxyz/reth) | Erigon: 13.5 / 15 <br/> EthereumJS: 4.5 / 8 <br/> Geth: 6 / 10 <br/> Grandine: 4 / 8 <br/> Besu: 12 / 15 <br/> Lighthouse: 11.5 / 15 <br/> Lodestar: 8 / 10 <br/> Nethermind: 13 / 15 <br/> Nimbus: 8 / 10 <br/> Prysm: 11 / 15 <br/> Teku: 10 / 12 <br/> Reth: 6 / 10 | | ||
|
There was a problem hiding this comment. I suggest setting the cap to at least 10 for all production grade clients. I also think that clients with a larger market share should have a higher cap than 10 (that's actually mostly reflected in the suggested caps except a few outliers). There was a problem hiding this comment. BTW, my comment was a hint that Grandine prefers to have a max cap of 10 too :) |
||
| | Client testing/security/infra <br/> which supports these implementations | - [ethereum/tests](https://github.com/ethereum/tests) <br/> - [ethereum/execution-spec-tests](https://github.com/ethereum/execution-spec-tests) | 2.5 / 5 | | ||
| | Network upgrade coordination | - [ethereum/pm](https://github.com/ethereum/pm) | 2 / 3 | | ||
| | Research and implementation experiments <br/> related to potential protocol changes | - [Verkle trees](https://github.com/gballet/go-verkle) (Verge) <br/> - [Portal Network](https://github.com/ethereum/portal-network-specs) (Purge) <br/> - [Ipsilon](https://github.com/ipsilon) (EVM Improvements) <br/> - Consensus work <br/> - Cryptography <br/> - Mechanism design <br/> - Resource pricing | Verkle Trees: 3 / 5 <br/> Portal Network: 7 / 10 <br/> EVM/Ipsilon: 4 / 8 <br/> Consensus Research: 12 / 15 <br/> Cryptography: 5 / 8 <br/> Mechanism Design: 5.5 / 8 <br/> Resource Pricing: 2 / 5 | | ||
|
There was a problem hiding this comment. I see that Protocol Security is missing, should that also be on the list? There was a problem hiding this comment. Yes, but probably in a different PR @fredriksvantes 😄 |
||
| | Protocol Guild | - Fundraising <br/> - Research/testing of future improvements <br/> - Internal maintenance of membership <br/> - General communications | 2 / 3 | | ||
|
|
||
| ## 1.1 Context | ||
|
|
||
|
|
@@ -35,5 +35,17 @@ Changing the eligibility framework can be made through a PR to the [documentatio | |
| - Name of project | ||
| - Eligibility start date for the project | ||
| - Summary of why this project should be considered eligible/ineligible | ||
| - Proposed member cap for the project | ||
| - Rationale for the proposed cap based on the project's scope, maturity, and expected contribution to the Ethereum protocol | ||
|
|
||
| The eligibility start date for the project is the date at which the project met the Eligibility criteria above. This is the earliest date that future Protocol Guild members can use to count contributions towards the project. | ||
|
|
||
| When proposing a new project, the member cap should reflect the project's current scope and maturity. Projects that wish to increase their cap must submit a separate PR with justification for the increase. This allows the Guild to maintain oversight of membership growth while ensuring each project has the resources it needs to contribute effectively to the protocol. | ||
|
|
||
| For the purpose of member caps, contributors with partial weight (0.5x) count as 0.5 towards their project's cap. For example, a project with a cap of 10 could include 8 full-weight members (counting as 8) and 4 partial-weight members (counting as 2) for a total of 10. | ||
|
|
||
| Projects that have reached their member cap must submit a PR to increase their cap before adding new members. The PR should include: | ||
| - Current number of members and their roles | ||
| - Justification for increasing the cap | ||
| - Impact of the increase on the overall Guild composition | ||
| - Expected timeline for utilizing the additional slots | ||
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.
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.
Why do we have Teku with 10 instead of 7? Or if we are considering 2 of the occasional contributors it would still be 9. Maybe I missed something? Or are these just "placeholder" values?
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 tried to make sense of it but I couldn't. Most likely placeholder values.
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.
Yeah, it's a placeholder. I should have clarified, sorry! I had an LLL count how many there were by project already and add a couple more buffers for larger projects 😄
I think we should either put all clients at like +33% from what they currently have for an initial cap, or the same number.