Matteo Georges
    • 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
    • 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 Versions and GitHub Sync Note Insights 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
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # Introduction Over the past two years, Liquid Staking has experienced extraordinary growth, with a cumulative total value locked across all liquid staking protocols on Ethereum reaching $44 billion in May 2024. This innovation has revolutionised DeFi by democratising access to native staking yields, previously limited to validators. Furthermore, it has facilitated compatibility across various protocols, offering enhanced yield opportunities. This rapid adoption has elevated Liquid Staking Tokens to a standard within DeFi. ![[LST TVL.png]] > Liquid Staking Token definition: *A liquid staking token is **a tokenised representation of staked assets**. When a user stakes their assets, they receive an equivalent amount of Liquid Staking Tokens. These LSTs can then be traded, sold, or used in other DeFi protocols, providing liquidity to the staker even while their original assets remain staked.* # Conventional Methods for Crypto-Asset Valuation In the current state of Oracle pricing, Liquid Staking Tokens (LSTs) are valued similarly to standard crypto-assets. The price is determined by aggregating data from various markets, including CEX and DEX, where the asset is traded. This approach is accurate and robust due to the market's deep liquidity. The high ratio between an asset's overall daily volume to its market capitalisation (Vol to MC) supports this method. Understanding the ratio between market capitalisation and daily volume is crucial for determining the robustness of an asset's price and its potential manipulation risk. Oracle prices are primarily used to calculate collateral amounts, such as in money market protocols. >**Note**: that in the following example, the total circulating supply remains fixed to facilitate the explanation. Consider a token with a market cap of $300 million and an overall daily volume of $25 million, resulting in a Vol to MC ratio of 8.334%. In the money market, a total of $20 million is used as collateral within the protocol. The next week, the market cap increases by 25%, bringing it to $375 million. Consequently, the total collateral for this asset in the money market also increases by 25%, rising to $25 million. Some money market users take advantage of this opportunity and increase their risk, getting closer to the maximum loan-to-value ratio. This increase in the asset's value attracts investor interest, raising the daily volume to $35 million. A few days later, the token's market cap drops by 10%, triggering a liquidation of $500,000 in the money market protocol. Thanks to its market deep liquidity, it can absorb the liquidation smoothly with minimal price impact. This liquidity limits the risk of bad debt for the protocol and reduces potential losses for lenders. Moreover we can state that the higher the MC grow, therefore the higher is the collateral opportunity but as the liquidity grows too, potential liquidation in that increase in collateral can be smoothly absorbed. # Contrasting with Liquid Staking/Restaking Tokens (LSTs/LRTs) > **Note**: For simplicity, the term ‘LSTs’ will be used to refer to both LSTs and LRTs throughout this document. However, when we turn to Liquid Staking Tokens (LSTs), the situation differs significantly. LSTs, while also traded on various markets, typically show lower Vol to MC ratios compared to standard crypto-assets. This suggests that increases in market cap do not necessarily correspond to proportional increases in liquidity. Therefore, pricing LSTs using the same methodology as standard crypto-assets might not be appropriate. LSTs often represent staked cryptocurrencies which are locked and thus may not contribute to trading volume as fluidly as unstaked assets. This can result in a liquidity profile that is markedly different from that of typical crypto-assets, necessitating a distinct approach to Oracle pricing that considers these unique characteristics. ==Graph with the top 50 crypto et top 20 LST/LRT== This difference in the ratio has a significant impact on the ability to liquidate position. Let's take another example to clarify the statement. - Standard token: as the MC grow, the national collateral amount in $ grows too but its liquidity. This research explores different methods to provide a more robust & efficient way of LST/LRT pricing. First it exist two different LST pricing mechanism: 1. Appreciation-based redistribution (mSOL, stSOL, wstETH) - Staking rewards are added to the pool, but the number of tokens remains constant. Each token represents the same share of a pool that increases in value over time due to the added rewards. As a result, the value of an individual token appreciates over time, mechanically increasing its price in the secondary market. 2. Issuance-based redistribution (stETH) - Staking rewards are paid out by increasing the supply of outstanding tokens, with the newly issued tokens being proportionally distributed among the staking participants. As a result, the price of each token is not directly impacted by the payout, as the rewards are distributed through the issuance of new tokens. ## Appreciation-based redistribution Method The mechanism for this type of LSTs is straightforward, as the staking rewards are automatically added to the pool. The price of an LST can be calculated by dividing the total number of staked tokens in the pool (totalStakedTokens) by the total number of LSTs in circulation (totalLSTInCirculation). This ratio represents the value of a single LST in terms of the underlying staked token: $$\frac{totalStakedTokens}{totalLSTInCirculation}$$ ### Pragma Approach ## Issuance-based redistribution Method - As the initial liquidity of ETH is not moved to its derivative LST or LRT, it means that their is a lower ETH is circulation meaning lower overall liquidity. Potential partners - [Rated](https://www.rated.network/home) - [Kiln](https://www.kiln.fi)

    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