bsci-filecoin
      • 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
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee
    • 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
    • Engagement control
    • Transfer ownership
    • Delete this note
    • 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 Sharing URL Help
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
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee
  • 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
    # The Impact of V1 Sector Expirations on Filecoin Storage and Cryptoeconomics ###### tags: `Articles` :::info Up to date by March 2021 ::: *Authors: Danilo Lessa Bernardineli (BlockScience)* ## Background context Shortly after Filecoin liftoff, a security issue was reported with the v1 proofs. The issue was fixed in v1.1 proofs, which were introduced in the Filecoin network version 7 upgrade, on November 25th, 2020. As a result of this upgrade: - All new sectors had to use v1.1 proofs - v1 sectors were allowed to remain on the network, **but were NOT allowed to be extended** Since the security of these sectors is not critically compromised, we can consider allowing their extension, which was proposed in [FIP-0014](https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0014.md). This report details the storage and cryptoeconomic impacts of allowing vs. rejecting FIP-0014. ## Executive Summary - The current size of the network is large enough to dillute the expiring sectors in April and May. - The network as measured in raw-bytes capacity is expected to continue growing during the V1 expiration wave. - It remains to the community to decide about the fairness and incentivization aspects of [FIP-0014](https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0014.md). The code and the visualizations for this writing can be seen on the following link: https://blockscience.github.io/filecoin-metrics/notebooks/fip_0014.html ## The first wave of expiring sectors Right now, Filecoin has about **92.3M active sectors, on which 26.2M (28% of the total) uses the V1 proof.** An immediate concern about them is about the sectors with 6 months lifetimes, as they're starting to expire on March 26, 2021, although the **majority is going to expire between 22 April, 2021 and 28 May, 2021, peaking on 10 May, 2021**. **That first wave makes up 6.3% of all Filecoin active sectors**, or 22.3% of all V1 sectors. In absolute terms, they're 5.8M sectors, or about 177PiB over three months. The big picture is contained in the following chart, where waves related to the 6 months, 12 months and 18 months sectors for both V1 and V2+ sectors are identified: ![Expiring sector count, monthly](https://hackmd.io/_uploads/SyGyv8U4_.png) A more granular view is obtained by getting the count on a daily window before 15 June. Note that the vertical axis is on logarithm scale. ![Expiring sector count, daily, before 15 june](https://hackmd.io/_uploads/SkUQD88Ed.png) Through the above figures, we can define key dates in regards to daily sector expiration rate: - 26 Mar, 2021: First sectors are expired - 14 Apr, 2021: Daily sector expiration rate is above 10k per day, or 312TiB per day. - 22 Apr, 2021: Daily sector expiration rate is above 100k per day, or 3.05PiB per day. - 10 May, 2021: Peak of the sector expiration rate, at about 201k per day, or 6.13PiB per day. - 28 May, 2021: Daily sector expiration rate gets below 10k per day, or 312TiB per day. ## Impact on Growth trends & Storage Power The **current forecast points towards having 3.8 EiB of raw-byte storage power by the end of May**. This is fuelled by the continued sealing of new sectors. ![Forecasted Raw Bytes Storage Power](https://hackmd.io/_uploads/B10j88vNd.png) --- We project that **the daily new sectors growth will be between 450k per day and 900k per day**, generating a **daily SP growth between 13.7 PiB per day to 27.5 PiB per day**. ![Forecasted Daily Sector growth](https://hackmd.io/_uploads/SypowvINO.png) ![](https://hackmd.io/_uploads/B1tw5vLNu.png) --- The expiration of approximately 5.8M sectors between 22 April and 28 May will subtract **180k per day** from the above numbers, which is equivalent to a reduction of **40% on the pessimistic side and 20% on the optimistic side.** Note that with more 64GiB sectors being added to the network, the actual impact tends towards the more optimistic case. ## Impact on Collateral Right now, **Filecoin has 27.8 Million FIL locked as sector collateral, 5.8M (21%) of which are on the V1 sectors**. Notice this is relatively lower than the sector share, as the collateral for each new sector tends to increase with time. **The 6 months V1 sectors have 1.2M FIL locked** with them (4.3% of the network total), and the event of their droppage should not be an issue for network security. ## Conclusions From a Cryptoeconomics point of view, the network will continue to be safe and healthy on any decision regarding allowing all V1 sectors to be extended to a maxium 540 days in epoch lifetime from their activation epoch. The decision of letting the V1 sectors expiring or not is to be put before the community, as there are multiple angles to FIP-0014 approval, which include considerations regarding fairness and behaviour incentivation, as well as other ones like environmental and waste minimization.

    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