Filecoin TL;DR

Staking Project Listing Policy

We want to ensure we reflect as many resources as possible while promoting transparency and confidence for users. Anyone is free to suggest adding a staking project or service on staking.filecointldr.io. If there’s one that we have missed, we would appreciate it if you could fill in the form Here. A Mandarin Chinese version is also available Here . For other enquiries or updates, please email [email protected]. While staking is still relatively new, we've tried to create a clear framework for consideration though the listing standards will change and evolve over time.

The decision framework

The decision to display a project on staking.filecointldr.io is not dependent on any one factor. Multiple criteria are considered together when deciding to display a project or service. The more of these criteria are met, the more likely it is to be displayed. This decision framework has been designed after the ethereum.org staking framework. Please see below for the question themes and the scoring framework.

Themes for inclusion

General

When was the project or service launched?

  • Is there evidence of when the project or service became available to the public?
  • This is used to determine the project’s "battle-tested" score.
  • Is the project being actively maintained?

Is there an active team developing the project?

  • Who is involved?
  • What jurisdiction is the team located in?

Note: Only actively maintained projects will be considered.

Do you have plans to launch natively on the Filecoin Virtual Machine?

  • If “Yes”, when will the solution be live on FVM?
  • This will be used to determine the project’s “FVM” score

Does the project have a liquidity incentive program to increase project adoption? If yes, please share a link to additional details

  • Solutions that plan to have a liquidity incentive program will be marked as so, but this will not contribute to or detract from a solution’s total score

Is the solution venture-backed? If so, by whom?

  • This will be used to calculate the “venture” score
  • Software and smart contracts

    Does the solution utilize smart contracts or a multi-sig approach?

    • If the solution utilizes a multi-sig, how many signers are required?

    Is everything open source?

    • Open-source projects should have a publicly available source code repository.
    • This is used to determine the project’s "open source" score.

    Is the project out of beta development?

    • Where is the project in its development cycle?
    • Projects in the beta stage are not considered for inclusion on staking.filecointldr.io

    What are the dependencies on services not directly on the Filecoin blockchain (i.e., off-chain oracles, bridges, other smart contracts, etc.)?

    • If yes, which ones?
    • This will not be attributed to any score, but will be listed alongside the listing.

    Has the software undergone an external security audit?

    • If yes, please upload or link the final audit report.
    • If not, are there plans to conduct an external audit?
    • This is used to determine the project’s "audited" score

    Does the project have a bug bounty program?

    • If not, are there plans to create a security bug bounty?
    • This is used to determine the project’s "bug bounty" score.

    Storage Provider Selection

    Which storage providers (and how many) are supported through this solution? Can the user choose? Can this change over time?

    • This is used to determine the project’s “multi-SP” score.

    How are Storage Providers selected for this staking pool?

    • This is used to determine the project’s “SP Selection” score.

    Are there capital limits on FIL lent out to any specific SP?

    • If “Yes”, do you have any documentation on these limits?
    • This is used to determine the project’s “capital limits” score.

    Staking Operations

    What is the minimum FIL required to stake?

    • e.g. 5 FIL
    • This is not used to calculate any specific score, but will be listed with the project.

    What are the fees associated with using the service?

    • What is the fee structure, e.g. is there a monthly fee for the service?
    • Any additional staking requirements?
    • This is not used to calculate any specific score, but will be listed with the project.

    Are users required to sign-up for an account?

    • Can someone use the service without permission or KYC?
    • This is used to determine the project’s "permissionless" score.

    Who holds the signing keys, and withdrawal keys?

    • What keys does the user maintain access to? What keys does the service gain access to?
    • This is used to determine the project’s "trustless" score.

    What is the token-holder diversity of those contributing to this project?

    • How many unique token-holders have contributed to the current TVL of your staking solution? What type of FIL token holders are best suited for contributing FIL to this project?
    • This is used to determine the project’s “diverse token-holder” score.

    Is there a liquidity token?

    • What are the tokens involved? How do they work? What are the contract addresses? Please describe how and over what time period FIL can be redeemed for the staked representations of FIL.
    • This is used to determine the project’s “diverse token-holder” score.