HackMD
  • Prime
    Prime  Full-text search on all paid plans
    Search anywhere and reach everything in a Workspace with Prime plan.
    Got it
    • Prime  Full-text search on all paid plans
      Prime  Full-text search on all paid plans
      Search anywhere and reach everything in a Workspace with Prime plan.
      Got it
      • Sharing Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • More (Comment, Invitee)
      • Publishing
        Everyone on the web can find and read all notes of this public team.
        After the note is published, everyone on the web can find and read this note.
        See all published notes on profile page.
      • Commenting Enable
        Disabled Forbidden Owners Signed-in users Everyone
      • Permission
        • Forbidden
        • Owners
        • Signed-in users
        • Everyone
      • Invitee
      • No invitee
      • Options
      • Versions and GitHub Sync
      • Transfer ownership
      • Delete this note
      • Template
      • Insert from template
      • Export
      • Dropbox
      • Google Drive
      • Gist
      • Import
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
      • Download
      • Markdown
      • HTML
      • Raw HTML
    Menu Sharing Help
    Menu
    Options
    Versions and GitHub Sync Transfer ownership Delete this note
    Export
    Dropbox Google Drive Gist
    Import
    Dropbox Google Drive Gist Clipboard
    Download
    Markdown HTML Raw HTML
    Back
    Sharing
    Sharing Link copied
    /edit
    View mode
    • Edit mode
    • View mode
    • Book mode
    • Slide mode
    Edit mode View mode Book mode Slide mode
    Note Permission
    Read
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    Write
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    More (Comment, Invitee)
    Publishing
    Everyone on the web can find and read all notes of this public team.
    After the note is published, everyone on the web can find and read this note.
    See all published notes on profile page.
    More (Comment, Invitee)
    Commenting Enable
    Disabled Forbidden Owners Signed-in users Everyone
    Permission
    Owners
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Invitee
    No invitee
       owned this note    owned this note      
    Published Linked with GitHub
    Like BookmarkBookmarked
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # Lido Operator Set Strategy - DRAFT ``` STATUS: Open for comment ``` ## ToC * [Introduction](#Introduction) * [Core Principles](#Core-Principles) * [Lido on Ethereum Principles & Guidelines](#Lido-on-Ethereum-Principles-amp-Guidelines) ## Introduction Lido’s product is dual-faceted: it provides liquid staking tokens to users and it provides operator sets which enable the liquid staking tokens to the protocols. The better the underlying operator sets are, the more robust, resilient, and performant the underlying protocol. Good operator sets boost the effectiveness of our business development efforts, increase community acceptance, and reduce protocol risks. Trustless and decentralized sets are necessary not only for the health of the underlying network, but also for Lido to reach its full potential in terms of AUM. Our thesis is that when liquid staking wins, it wins hard. Having a robust operator set is a precondition for this success to be sustainable. The more decentralized Lido’s operator sets are, the less risky it is for an increased amount of assets to be staked with it – not only to stakers themselves, but also in terms of possible effects to integrated DeFi protocols and the underlying networks. As a bedrock protocol, Lido must strive to ensure that the operators (and their validators) it selects or delegates to comprise a set that is net positive for the underlying protocol. While in certain cases pragmatic constraints (e.g. the possible set given the market demand for the staked token) may lead to sub-optimally decentralized, or permissioned sets, the strategy must always include a plan describing what’s required for the set to evolve into the maximally decentralized and permissionless version of itself. In each protocol that Lido operates on, it will need to develop a tailored operator set strategy that addresses the respective staking environment, technical complexities, and community expectations. In addition, it is important for Lido to have an abstract and cohesive overall strategy that guides the specific strategies for each chain/network. The operator strategy for each network/chain that Lido operates on should use the *Core Principles* as a set of base principles from which to develop specific guidelines tailored to each specific network/chain. ## Core Principles It is important to recognize that the objective of Lido is what ultimately drives both its actual usage and its import within the context of the multi-chain world that it inhabits. As we attempt to build a “better substitute” for native tokens, this means that the ultimate goal of Lido is to replace native tokens whenever possible which also means that the security, fragility, and overall ecosystem impacts of its liquid staking tokens should be as close to that of the native tokens as possible. In other words, Lido should strive to build offerings that are net-positive for the chains that it inhabits (i.e. provide value without making concessions in the health of the underlying protocol), which necessitates that ecosystem stewardship, not profitability, is our primary concern. Lido operator set strategies should adhere to the following core principles: - Lido’s operator set should increase the robustness, security, reliability, and decentralization of the underlying protocol (when compared to the most likely alternative that would be created by market forces); - Lido’s operator set should be maximally decentralized and distributed given current network and market constraints; - Lido’s operator set should include considerations to mitigate the possibility of one or a select-few parties operating or controlling an inordinate amount of stake in any protocol through Lido stake; - Lido’s operator set should take into account ecosystem participation and stewardship, and support smaller organizations which vitally contribute to validating and staking; - Lido’s operator set should select for distribution and decentralization in combination with optimal performance and profitability (the former should not be sacrificed for the latter). ## Lido on Ethereum Principles & Guidelines The purpose of this section is to describe principles, guidelines, and goals of the current strategy. At the same time, we should be thinking about what the strategy for the following six months may look like, and what the strategy post-withdrawals, DVT, etc. may look like. In addition to the [Core Principles](#Core-Principles), Ethereum has an additional focus on client diversity; Lido should be a force for better client diversity. - Lido’s operator set should improve overall client diversity on Ethereum - No one node operator should have > 1% of total ETH staked via Lido - Node operators should run execution layer and consensus layer nodes specifically for the validators that they operate for Lido - Node operators should be distributed jurisdictionally - Validators should be distributed geographically - Validators should be distributed in terms of infrastructure: - No overreliance on cloud providers; - No overreliance specific data center providers. - Operators should be using best practices for securing their execution layer and consensus layer nodes, as well as their validator clients - Operators should be using best practices for key management and security of keys - Until withdrawals and a robust permissionless node operator registry is possible, a curated set of professional node operators, consisting of both established multi-chain operators as well as new entrants and operators who focus specifically on Ethereum, is the best way to safeguard user deposits, keys, and the exit+withdrawal process - Operators in the curated set should not be running white-label nodes (i.e. using another operator behind the scenes) - Following the possibility for triggerable exits and withdrawals, there should be a stake (re)-balancing mechanism put in place that: - Rewards (gives more stake to) operators who promote the above objectives; - Derisks (removes stake from) operators who are reaching the theoretical limit, and/or are not performing optimally, and/or whose participation negatively affects Lido’s overall effectiveness with regards to the above objectives; - Allows newer and smaller operators to join the set and work their way up. ###### tags: `node operators` `validators` `strategy` `principles` `guidelines`

    Import from clipboard

    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 lost their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template is not available.


    Upgrade

    All
    • All
    • Team
    No template found.

    Create custom template


    Upgrade

    Delete template

    Do you really want to delete this template?

    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

    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

    Tutorials

    Book Mode Tutorial

    Slide Mode Tutorial

    YAML Metadata

    Contacts

    Facebook

    Twitter

    Feedback

    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

    Versions and GitHub Sync

    Sign in to link this note to GitHub Learn more
    This note is not linked with GitHub Learn more
     
    Add badge Pull Push GitHub Link Settings
    Upgrade now

    Version named by    

    More Less
    • Edit
    • Delete

    Note content is identical to the latest version.
    Compare with
      Choose a version
      No search result
      Version not found

    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. Learn more

         Sign in to GitHub

        HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.

        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
        Available push count

        Upgrade

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Upgrade

        Danger Zone

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

        Syncing

        Push failed

        Push successfully