DanGoron
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # Week 1 Dev update Thrilled to be part of the 5th Ethereum Protocol Fellowship cohort! We had the kick-off call on Monday the 10th June, and the office hours meeting on Tuesday. One thing that stuck with me is to approach the core development/research in a holistic way, outside of just the strict scope of my project and get a bird's-eye view of the protocol's roadmap and where everything is heading to, while understanding that there are real people all around the world involved in the process and that implementing one's goals in core dev/research means interacting with peers and disseminating as much as possible. ## Week 1 topics This week I started broadening my protocol study and research on topics I feel will help me better understand the protocol and core development / research, and take the deep dive into these topics while advancing towards my objectives. The broader goals of my project, being to introduce Delegators as a new class in beacon state and to separate protocol services into a heavy class and a light class, is reflected in this week's study. ### Serenity design rationale Vitalik's Serenity (Phase 0) design rationale[^1] helped me understand the thinking behind the beacon chain specification[^2], the Validator life cycle and to formulate a high-level approach on how the `class Delegators` container can be added while introducing as few consensus-specs breaking changes as possible. ### Delegating validators I studied a closed (late) 2021 consensus-specs PR from @potuz,[^3] regarding delegating validators. Although never materialized, being obsoleted by the withdrawal upgrades, it's a good read on the possibility of in-protocol delegations. The gist was that by adding new (`delegation`) fields in existing containers, validators can delegate excess winnings to other validators within the consensus layer, without involving the deposit contract. ### p2p messaging in CL I started diving into the consensus p2p-interface[^4] this week, to get a deeper understanding of how consensus participants gossip consensus payload using messages and topics. ### SSF As I mentioned in my [week 0](https://hackmd.io/9q92KZ-CRO-k9NCF5agAJw#Project-motivation) update, one topic I find most interesting in R&D space, is staking economics in the context of Single Slot Finality. Working on the eODS writeup for epf.wiki, I realized that the vertical dimension of the Operator Delegator separation could have positive externalities for the SSF roadmap[^5], so this week I continued to study Fellowship alumni Lincoln Murr's development updates on his SSF-overview project of cohort-4. I'll continue with studying his MASTER OF SCIENCE paper[^6], and exchanging opinions with him about how splitting staking into a heavy & a light layer could help determining the right validator subsampling and validator economics in an SSF scenario.[^7] ### Ethereum PM I read [Nyota ACD](https://notes.ethereum.org/@timbeiko/acd-nyota), and [ethereum/pm issues](https://github.com/ethereum/pm/issues), as I plan to get up to speed periodically on project management. I joined the [CL call #135](https://github.com/ethereum/pm/issues/1069) on Thursday, and noted the following: * Tim Beiko's Review request for the PFI/CFI/SFI status of EIPs: [EIP-7723](https://github.com/ethereum/EIPs/pull/8662). I left a comment, as I think these are good additions, that can bring more clarity in tracking the status of an EIP during the network upgrade process. * Devs are called to [vote](https://ethereum-magicians.org/t/f-star-name-for-consensus-layer-upgrade-after-electra/20285/1) for the F-star name for Consensus Layer upgrade after Electra. I voted for Fulu. * [SSZ update](https://github.com/ethereum/pm/issues/1069#issuecomment-2162556692). EIP-7688 proposes transitioning consensus SSZ data structures to StableContainer[^9]. I plan to study StableContainer starting next week. * [PeerDAS is added to the list of Pectra EIPs](https://github.com/ethereum/EIPs/pull/8649) in the Meta EIP. * Electra devnet-1 * specs release [v1.5.0-alpha.3](https://github.com/ethereum/consensus-specs/pull/3786). I'm bound to following Electra specs releases, since the changes in my project will be based on Electra specs. * There was debate about introducing new fields in the middle of an existing Container, breaking merkleization of subsequent fields. I needed to deepen my knowledge in serialization so I'm leveraging epf.wiki pages on SSZ[^10] and merkleization[^11], and also the design rationale paper.[^1] ### Timing Games in Proof of Stake consensus protocols I thoroughly read during week 1 the *Time is Money: Strategic Timing Games in Proof-of-Stake Protocols* research paper on Timing Games[^12]. It's the first formal analysis of this relatively new concept in Ethereum, one that will have implications in the way PBS gets implemented and in the Attester Proposer Separation research space. For the scope of Operator Delegator Separation, and in the context of Timing Games, I will try to find out during my project's research part if there could exist a [Nash equilibria](https://en.wikipedia.org/wiki/Nash_equilibrium), involving Validators and Light service providers[^13] (Delegators or Solo stakers) as [preference entropy](https://ethresear.ch/t/unbundling-staking-towards-rainbow-staking/18683) generators? What would the equilibrium equations look like? ## Week 2,3 planning - Study Deposit contract - I intend to contact staking pools to get an early sentiment on how the changes I might propose in the project would influence staking. I'll have a call with a permissionless stakin protocol, e.g. Geode or Stakewise - I intend to write the Timing Games epf.wiki page during next week - More SSF studies - Study EIP-7495: SSZ StableContainer[^8] ## Resources for week 1 [^1]: https://notes.ethereum.org/@vbuterin/serenity_design_rationale [^2]: https://github.com/ethereum/consensus-specs [^3]: https://github.com/ethereum/consensus-specs/pull/2763 [^4]: https://github.com/ethereum/consensus-specs/blob/2360756c8c19c0f7b0e91135f5bbcddecdf0a835/specs/phase0/p2p-interface.md#topics-and-messages [^5]: https://epf.wiki/#/wiki/research/eODS?id=the-two-tier-staking-approach-to-ssf [^6]: https://ir.vanderbilt.edu/bitstream/handle/1803/18820/MURR-THESIS-2024.pdf?sequence=1&isAllowed=y [^7]: https://notes.ethereum.org/@vbuterin/single_slot_finality#What-are-the-key-questions-we-need-to-solve-to-implement-single-slot-finality [^8]: https://eips.ethereum.org/EIPS/eip-7495 [^9]: https://eips.ethereum.org/EIPS/eip-7688 [^10]: https://epf.wiki/#/wiki/CL/SSZ [^11]: https://epf.wiki/#/wiki/CL/merkleization [^12]: https://arxiv.org/pdf/2305.09032 [^13]: https://epf.wiki/#/wiki/research/eODS?id=delegators-role-under-eods

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully