-
Notifications
You must be signed in to change notification settings - Fork 104
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #109 from eth-protocol-fellows/main
Update wiki, Mar 21
- Loading branch information
Showing
11 changed files
with
108 additions
and
11 deletions.
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
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
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
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
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 |
---|---|---|
@@ -0,0 +1,27 @@ | ||
# Study Group Week 6 | Consensus and Execution spec | ||
|
||
The development track of week 6 will provide a deeper insight into consensus and execution layer specification. | ||
|
||
Join the presentation by [Hsiao-Wei](https://twitter.com/icebearhww) and [Sam](https://twitter.com/_SamWilsn_) on [Monday, March 25, 2PM UTC](https://savvytime.com/converter/utc-to-germany-berlin-united-kingdom-london-ny-new-york-city-ca-san-francisco-china-shanghai-japan-tokyo-australia-sydney/mar-18-2024/4pm). (Note it's 2 hour earlier than our regular calls!) | ||
|
||
The talk will be streamed live on [StreamEth](https://streameth.org/65cf97e702e803dbd57d823f/epf_study_group) and Youtube, links will be provided before the call in the [Discord server](https://discord.gg/addwpQbhpq). Discord also serves for the discussion and questions during the stream. | ||
|
||
## Pre-reading | ||
|
||
Before starting with the week 6 content, make yourself familiar with resources in previous weeks, especially 1-3. | ||
|
||
Additionally, you can read get ready by studying following resources: | ||
|
||
- https://github.com/ethereum/consensus-specs | ||
- https://blog.ethereum.org/2023/08/29/eel-spec | ||
- https://github.com/ethereum/execution-specs | ||
|
||
## Outline | ||
|
||
- HWW on Consensus specs | ||
- Sam on EELS | ||
|
||
## Additional reading and exercises | ||
|
||
- https://ethereum.org/en/developers/tutorials/yellow-paper-evm/ | ||
- https://eth2book.info/capella/annotated-spec/ |
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
File renamed without changes.
Binary file not shown.
Binary file not shown.
Binary file not shown.
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 |
---|---|---|
@@ -0,0 +1,47 @@ | ||
# MINIMUM VIABLE ENSHRINEMENT OF LIQUID STAKING (MVE-LS) | ||
|
||
## What is MVE-LS? | ||
MVE-LS is the minimum set of measures that could be implemented at protocol level in a short period of time (preferably in parallel with other congruent upgrades being developed and evaluated for inclusion in Pectra hard fork). | ||
It is the quasi-equivalent of Level 1/3 as per the [Rainbow Staking POC](https://ethresear.ch/t/unbundling-staking-towards-rainbow-staking/18683/8) - Enshrined Operator-Delegator separation: | ||
|
||
``` | ||
[...]enshrining some separation between operator and delegator[...] might be ok with some level of complexity. We could call a basic operator/delegator separation Level 1 [...] | ||
``` | ||
[[1]](#resources) | ||
|
||
## Feasibility | ||
* Necessity | ||
- There are risks in relying too much on the social layer and morality to protect the protocol against centralization in the staking scene and countering the emergence of a dominant LST with its afferent perils | ||
- We need an interface to integrate further “protocol services” in a plug-and-play manner | ||
- Limitations of current staking-design to ensure future competitive participation of solo stakers in different categories of protocol services (i.e. economic value and/or agency) | ||
- Ethereum needs good trade-offs to SSF | ||
* Opportunity | ||
- enshrining a variant of the already established staking model with two classes of participants: delegators (stakers) and node operators | ||
- enshrining some measure of operator–delegator separation concomitant with other EIPs that are debated and developed right now, could leverage a lot of the work currently done towards specifying these EIPs: | ||
- EIP-6110 [[5]](#resources) allows for an in-protocol mechanism of deposit processing on the Consensus Layer. Also it will add in-protocol mechanism by which large node operators can combine validators without cycling through the exit and activation queues. | ||
- EIP-7251 [[4]](#resources) will allow a single message to carry more stake; enshrining the operator delegator separation would provide a way for the protocol to functionally distinguish “operator stake” from “delegator stake” on such a message. | ||
|
||
## Feature set | ||
|
||
| **FEATURE** | **title** | **description** | | ||
| :----------: | :-----------: | :-----------: | | ||
|Feature 1|enshrine Quick Staking Key (Q key)|Allow validators to provide two staking keys: the persistent key (P key) and the quick staking key (Q key) - a smart contract that, when called, outputs a secondary staking key during each slot | ||
|
||
``` | ||
The protocol would give powers to these two keys, but the mechanism for choosing the second key in each slot could be left to staking pool protocols. | ||
``` | ||
[[2]](#resources) | ||
## Implementation POC | ||
MVE-LS POC can be done on top of EIP-6110 specification for future validator deposits and of EIP-7251 for backward compatibility (hard fork) | ||
|
||
## Resources | ||
[[1] Unbundling staking](https://ethresear.ch/t/unbundling-staking-towards-rainbow-staking/18683) | ||
|
||
[[2] Protocol and staking pool changes that could improve decentralization and reduce consensus overhead](https://notes.ethereum.org/@vbuterin/staking_2023_10) | ||
|
||
[[3] Should Ethereum be okay with enshrining more things in the protocol?](https://vitalik.eth.limo/general/2023/09/30/enshrinement.html#what-do-we-learn-from-all-this) | ||
|
||
[[4] EIP-7215](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-7251.md) | ||
|
||
[[5] EIP- 6110](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-6110.md) | ||
|