diff --git a/SUMMARY.md b/SUMMARY.md index fbb41867f..4f3b99651 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -35,7 +35,7 @@ * [Serving retrievals](basics/how-retrieval-works/serving-retrievals.md) * [Saturn](basics/how-retrieval-works/saturn.md) * [Project and community](basics/project-and-community/README.md) - * [Chat and discussion forums](basics/project-and-community/chat-and-discussion-forums.md) + * [Forums and FIPs](basics/project-and-community/forums-and-FIPs.md) * [Filecoin compared to](basics/project-and-community/filecoin-compared-to.md) * [Filecoin FAQs](basics/project-and-community/filecoin-faqs.md) * [Related projects](basics/project-and-community/related-projects.md) diff --git a/basics/how-storage-works/filecoin-plus.md b/basics/how-storage-works/filecoin-plus.md index 3c3cea59e..4336167e8 100644 --- a/basics/how-storage-works/filecoin-plus.md +++ b/basics/how-storage-works/filecoin-plus.md @@ -99,6 +99,6 @@ There are three resources you can use to check the current status of the Filecoi * The [Datacap Stats dashboard](https://datacapstats.io) shows DataCap allocations, including the number of allocators, clients, and storage providers. You can also see number and size of deals. * The [Starboard Dashboard](https://dashboard.starboard.ventures/market-deals) includes network health data related to Filecoin+ verified deals. - +To learn more about Filecoin Plus, review [FIP003: Filecoin Plus Principles](https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0003.md). [Was this page helpful?](https://airtable.com/apppq4inOe4gmSSlk/pagoZHC2i1iqgphgl/form?prefill\_Page+URL=https://docs.filecoin.io/basics/how-storage-works/filecoin-plus) diff --git a/basics/how-storage-works/storage-onramps.md b/basics/how-storage-works/storage-onramps.md index 3fa589464..c17f06664 100644 --- a/basics/how-storage-works/storage-onramps.md +++ b/basics/how-storage-works/storage-onramps.md @@ -6,20 +6,15 @@ description: >- # Storage onramps -Here’s how they work: Developers use APIs or libraries to send data to storage helpers. Behind the scenes, storage helpers receive the data and handle the underlying processes to store it in a reliable and decentralized storage way by saving it [IPFS](https://ipfs.tech) nodes, making deals with Filecoin storage providers – or both. You can use the same APIs or other tools to retrieve data quickly. - -Storage helpers are available for NFTs (non-fungible tokens) or general data. If you are storing NFTs, check out [Storing NFTs](storage-onramps.md#storing-nfts). For general data, skip to [General data storage](storage-onramps.md#general-data-storage). - -#### Storing NFTs - -* [The NFT.Storage flagship product](https://nft.storage/nft-storage-flagship-product) focuses on the enduring preservation of NFTs with a low one-time fee per. First mint your NFTs, then send us the NFT data that we preserve in endowment-backed long-term Filecoin storage. As an NFT.Storage user, you support our platform when you choose Pinata and Lighthouse for hot storage and [use our referral links here](https://nft.storage/blog/announcing-our-new-partnerships-with-pinata-and-lighthouse), helping to sustain our valuable public goods. Your NFTs will also be included in the NFT Token Checker, a tool for block explorers, marketplaces and wallets to show verification that NFT collections, tokens, and CIDs are preserved by NFT.Storage. -* [NFT.Storage Classic](https://nft.storage/nft-storage-classic) is a free service that provides hot data storage on the decentralized Filecoin network with fast retrieval through IPFS. As of June 30, 2024, we have officially decommissioned NFT.Storage Classic uploads, however retrieval of existing data remains operational. For NFT data already uploaded through NFT.Storage Classic, the NFT.Storage Gateway makes the data retrievable on block explorers, marketplaces and dapps. - -#### General data storage - -* [Chainsafe Storage API](https://docs.storage.chainsafe.io) is an underlayer to Chainsafe’s encrypted IPFS & Filecoin file storage system. It offers S3-compatible bucket-style APIs for easy migration of data. As of September 2022, it’s the only storage helper with built-in encryption. -* [Web3.Storage](https://web3.storage/docs) is a fast and open developer platform for [storing and interacting with data](https://blog.web3.storage/). Upload any data and Web3.Storage will ensure it ends up on a decentralized set of IPFS and Filecoin storage providers. There are JavaScript and Go libraries for the API, as well as a no-code web uploader. Free and paid plans are available. +Developers use web UIs, APIs, or libraries to send data to storage onramps. Behind the scenes, storage onramps receive the data and handle the underlying processes to store it in a reliable way, making deals with Filecoin storage providers. +The available storage onramps are: +* [Lighthouse](https://lighthouse.storage/) "offers permanent, decentralized storage powered by Filecoin. Secure, scalable, and ideal for individuals, developers, and enterprises." +* [Akave](https://www.akave.ai/) is "revolutionizing data management with a decentralized, modular solution that combines the robust storage of Filecoin with cutting-edge encryption and easy-to-use interfaces." +* [Storacha](https://storacha.network/) is an open hot storage network scales IPFS and Filecoin. Upload any data and Storacha will ensure it ends up on a decentralized set of IPFS and Filecoin storage providers. There Storacha [docs](https://docs.storacha.network/) detail the JavaScript and Go API libraries, and there is a no-code web uploader available as well. +* [Singularity](https://singularity.storage/) "facilitates onboarding of large quantaties of data (PB-scale) to the Filecoin network in an efficient, secure, and flexible way." +* [CID Gravity](https://www.cidgravity.com/) is a "seamless gateway to the decentralized web", allowing you to drag and drop files through an easy-to-use UI that uploads files to Filecoin and IPFS. +* [Ramo](https://www.ramo.io/) is "a network coordinating people, hardware and capital to build a more open and resilient internet infrastructure for everyone." [Was this page helpful?](https://airtable.com/apppq4inOe4gmSSlk/pagoZHC2i1iqgphgl/form?prefill\_Page+URL=https://docs.filecoin.io/basics/how-storage-works/storage-onramps) diff --git a/basics/project-and-community/chat-and-discussion-forums.md b/basics/project-and-community/chat-and-discussion-forums.md deleted file mode 100644 index 70a53d375..000000000 --- a/basics/project-and-community/chat-and-discussion-forums.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -description: >- - Connect with the Filecoin community in discussion forums or on IRC. The - Filecoin community is active and here to answer your questions in your channel - of choice. ---- - -# Chat and discussion forums - -### Chat - -For shorter-lived discussions, our community chat open to all on both Slack and Matrix, with bridged channels allowing you to participate in the same conversations from either platform: - -* [Slack](https://filecoin.io/slack/) -* [Matrix](https://matrix.to/#/#ipfs-space:ipfs.io) - -### Discussion Forums - -For long-lived discussions and for support, please use the [discussion tab on GitHub](https://github.com/filecoin-project/community#forums) instead of Slack or Matrix. It’s easy for complex discussions to get lost in a sea of new messages on those chat platforms, and posting longer discussions and support requests on the forums helps future visitors, too. - - - -[Was this page helpful?](https://airtable.com/apppq4inOe4gmSSlk/pagoZHC2i1iqgphgl/form?prefill\_Page+URL=https://docs.filecoin.io/basics/project-and-community/chat-and-discussion-forums) diff --git a/basics/project-and-community/forums-and-FIPs.md b/basics/project-and-community/forums-and-FIPs.md new file mode 100644 index 000000000..fc4230001 --- /dev/null +++ b/basics/project-and-community/forums-and-FIPs.md @@ -0,0 +1,40 @@ +--- +description: >- + Connect with the Filecoin community in discussion forums or on IRC. The + Filecoin community is active and here to answer your questions in your channel + of choice. +--- + +# Discussion Forums and Filecoin Improvement Proposals + +### Discussion Forums + +For shorter-lived discussions, our community chat open to all on both Slack and Discord: + +* [Slack](https://filecoin.io/slack/) +* [Discord](https://discord.com/invite/filecoin) + +For long-lived discussions and for support, please use the [discussion tab on GitHub](https://github.com/filecoin-project/community#forums) instead of Slack. It’s easy for complex discussions to get lost in a sea of new messages on those chat platforms, and posting longer discussions and support requests on the forums helps future visitors, too. + +### Filecoin improvement proposals + +Filecoin improvement proposals (FIPs) are design documents that propose changes and improvements to the Filecoin network, giving detailed specifications and their rational, and allowing the community to document their consensus or dissent. All technical FIPs that are accepted are later reflected in the [Filecoin Spec](https://spec.filecoin.io/). + +There are three types of FIPs: +* Technical FIPs (FTP): protocol changes, standards, API changes. They can include core (consensus-related changes, networking (network protocol improvements, interface (API/RPC or language-level updates), or can be informational (updates to general guidelines or documentation). +* Organizational FIPs (FOP): changes to processes, tools, or governance. +* Recovery FIPs (FRP): emergency fixes requiring state changes (e.g., major bugs). + +Typically, the FIP lifecycle looks something like this: + +[ WIP ] -> [ DRAFT ] -> [ LAST CALL ] -> [ ACCEPTED ] -> [ FINAL ] + +1. WIP: A community member has an idea for a FIP, and begins discussing the idea publicly on the Filecoin Discord, in the [Filecoin Slack channel for discussing FIPs](https://filecoinproject.slack.com/archives/C01EU76LPCJ), or in Github issues for the relevant repo. +2. DRAFT: If there is a chance the FIP could be adopted, the author submits a draft for the FIP as a pull request in the [FIPs repo](https://github.com/filecoin-project/FIPs). +3. LAST CALL: This status allows the community to submit final changes to the draft. +4. ACCEPTED: Once the FIP is voted on and accepted, the core engineers will work to implement it. +5. FINAL: This status represents the current state-of-the-art, and it should only be updated to correct errors. + +It is the authors' responsibility to request status updates for the FIP. A more robust explainer of the FIP process can be found in [FIP001](https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0001.md#what-is-a-fip). + +[Was this page helpful?](https://airtable.com/apppq4inOe4gmSSlk/pagoZHC2i1iqgphgl/form?prefill\_Page+URL=https://docs.filecoin.io/basics/project-and-community/chat-and-discussion-forums) diff --git a/basics/project-and-community/ways-to-contribute.md b/basics/project-and-community/ways-to-contribute.md index 2cf91588e..212244786 100644 --- a/basics/project-and-community/ways-to-contribute.md +++ b/basics/project-and-community/ways-to-contribute.md @@ -39,7 +39,7 @@ If you have never contributed to an open-source project before, or just need a r #### Community -If interacting with people is your favorite thing to do in this world, join the [Filecoin chat and discussion forums](chat-and-discussion-forums.md) to say hello, meet others who share your goals, and connect with other members of the community. You should also consider joining [Filecoin Slack](https://filecoin.io/slack). +If interacting with people is your favorite thing to do in this world, join the [Filecoin chat and discussion forums](forums-and-FIPs.md) to say hello, meet others who share your goals, and connect with other members of the community. You should also consider joining [Filecoin Slack](https://filecoin.io/slack). #### Build Applications diff --git a/basics/the-blockchain/drand.md b/basics/the-blockchain/drand.md index 4183701b8..e775bbbcc 100644 --- a/basics/the-blockchain/drand.md +++ b/basics/the-blockchain/drand.md @@ -6,7 +6,7 @@ description: >- # Drand -This page covers how Drand is used within the Filecoin network. For more information on Drand generally, [take a look at the project’s documentation](https://drand.love/docs). +This page covers how Drand is used within the Filecoin network. For more information on Drand generally, [take a look at the project’s documentation](https://www.drand.love/developers). ## Randomness outputs diff --git a/basics/what-is-filecoin/crypto-economics.md b/basics/what-is-filecoin/crypto-economics.md index 72f59bbe8..d9affa6d9 100644 --- a/basics/what-is-filecoin/crypto-economics.md +++ b/basics/what-is-filecoin/crypto-economics.md @@ -25,7 +25,11 @@ Additionally, 300 million FIL tokens are held in a mining reserve to incentivize ## Vesting -Mining rewards are subject to a vesting schedule to support long-term network alignment. For instance, 75% of block rewards earned by miners vest linearly over 180 days, while 25% are immediately accessible, improving miner cash flow and profitability. Further, FIL tokens are vested to Protocol Labs teams and the Filecoin Foundation over six years and to SAFT investors over three years, as outlined in the vesting schedule. +Mining rewards are subject to a vesting schedule to support long-term network alignment. For instance, 75% of block rewards earned by miners vest linearly over 180 days, while 25% are immediately accessible, improving miner cash flow and profitability. Note that if the miner has incurred "[fee debt](https://docs.filecoin.io/storage-providers/filecoin-economics/slashing)," the immediately accessible block rewards will automatically go towards paying down those fees. + +A certain portion of initially printed FIL tokens are vested to Protocol Labs teams and the Filecoin Foundation over six years, and to SAFT investors over three years, as outlined in the [vesting schedule](https://observablehq.com/@starboard/a-primer-to-filecoin-circulating-supply/2). + +To learn more about Filecoin block rewards vesting, review [FIP004: Liquidity Improvement for Storage Miners](https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0004.md). ## Collateral and slashing diff --git a/networks/calibration/rpcs.md b/networks/calibration/rpcs.md index 5c0435602..2288d783b 100644 --- a/networks/calibration/rpcs.md +++ b/networks/calibration/rpcs.md @@ -42,10 +42,5 @@ FULLNODE_API_INFO=wss://wss.calibration.node.glif.io/apigw/lotus lotus daemon -- * When using a lite-node, omit `/rpc/v1` from Glif’s WebSocket address. * [Glif documentation](https://hosting.glif.io/) -## [Lava](https://docs.lavanet.xyz/filecoin) - -* HTTPS: `https://filecoin-testnet.lava.build` -* [Lava documentation](https://docs.lavanet.xyz/filecoin-dev) - [Was this page helpful?](https://airtable.com/apppq4inOe4gmSSlk/pagoZHC2i1iqgphgl/form?prefill\_Page+URL=https://docs.filecoin.io/networks/calibration/rpcs) diff --git a/networks/mainnet/rpcs.md b/networks/mainnet/rpcs.md index 4a65c4696..431e7a887 100644 --- a/networks/mainnet/rpcs.md +++ b/networks/mainnet/rpcs.md @@ -20,7 +20,7 @@ In order to check the current benchmarked performance of each of the below endpo | [Ankr](https://ankr.com/) | `https://rpc.ankr.com/filecoin` | By request at: https://www.ankr.com/rpc/filecoin | [Ankr Docs - Filecoin](https://www.ankr.com/docs/rpc-service/chains/chains-list/#filecoin) | All Filecoin and Eth JSON RPC methods including MPoolPush | | [Chainup Cloud](https://cloud.chainup.com/) | `https://filecoin.chainup.net/rpc/v1` | `wss://filecoin.chainup.net/rpc/v1` | [Chainup Cloud Docs - Filecoin](https://docs.chainupcloud.com/blockchain-api/filecoin/public-apis) | | | [NOWNodes](https://nownodes.io/) | `https://fil.nownodes.io` (Free for 1 month with signup) | | [NOWNodes - Docs](https://documenter.getpostman.com/view/13630829/TVmFkLwy) | | -| [Lava](https://docs.lavanet.xyz/filecoin-dev) | `https://filecoin.lava.build` | | [Lava - Docs](https://docs.lavanet.xyz/filecoin-dev) | JSON RPC | + ## Additional Notes: diff --git a/reference/general/README.md b/reference/general/README.md index fec7ea6b8..666e39dfd 100644 --- a/reference/general/README.md +++ b/reference/general/README.md @@ -23,7 +23,6 @@ description: >- * [Forest](https://github.com/ChainSafe/forest) - Rust. * Lotus Docker Hub Images (unofficial): * [`glif/lotus`](https://github.com/glifio/filecoin-docker) - * [`textile/lotus`](https://hub.docker.com/r/textile/lotus) ### Networks @@ -58,11 +57,15 @@ Tools to check status and details of the network and chain. * [`filecoin.tools`](https://filecoin.tools) - check your CID’s storage deal status. Also provides an API - check [`filecoin.tools/docs`](https://filecoin.tools/docs) for reference * [Deals list at `Filfox.io`](https://filfox.info/en/deal) -## Storage Web Applications +## Storage Onramps Web-based applications that store your data on Filecoin. No command-line or coding experience required. -* [ChainSafe Files](https://files.chainsafe.io/) - Dropbox-style UI, login with OAuth or general MetaMask +* [Lighthouse](https://lighthouse.storage/) "offers permanent, decentralized storage powered by Filecoin. Secure, scalable, and ideal for individuals, developers, and enterprises." +* [Storacha](https://storacha.network/) is an open hot storage network scales IPFS and Filecoin. Upload any data and Storacha will ensure it ends up on a decentralized set of IPFS and Filecoin storage providers. There Storacha [docs](https://docs.storacha.network/) detail the JavaScript and Go API libraries, and there is a no-code web uploader available as well. +* [Singularity](https://singularity.storage/) "facilitates onboarding of large quantaties of data (PB-scale) to the Filecoin network in an efficient, secure, and flexible way." +* [CID Gravity](https://www.cidgravity.com/) is a "seamless gateway to the decentralized web", allowing you to drag and drop files through an easy-to-use UI that uploads files to Filecoin and IPFS. +* [Ramo](https://www.ramo.io/) is "a network coordinating people, hardware and capital to build a more open and resilient internet infrastructure for everyone." * [Starling Framework for Data Integrity](https://www.starlinglab.org/) * to securely capture, store and verify human history * learn more at [`starlinglab.org/78days`](https://www.starlinglab.org/78days/) or the [Filecoin blog interview](https://filecoin.io/blog/starling-framework/) @@ -75,12 +78,9 @@ Developer tools, API clients & storage services that developers can use to build ### Storage APIs for app builders * [Lighthouse](https://www.lighthouse.storage/) - Lighthouse offers a suite of tools to enable builders to store data on Filecoin when building apps. -* [`NFT.storage`](https://nft.storage/) - Preserve your NFTs with our new low-cost, easy-to-use solution, ensuring verifiable long-term storage on Filecoin. -* [`Web3.storage`](https://web3.storage/) - service from Protocol Labs for storing off-chain _dApp_ data on IPFS and Filecoin, with help from Pinata (a fast IPFS Pinning Service) to [distribute the content across IPFS](https://www.pinata.cloud/blog/protocol-labs-and-pinata) -* [`Textile.io's tools`](https://docs.textile.io/) - suite of tools for interacting with IPFS and Filecoin, including [Tableland](https://tableland.xyz/) and Filecoin bridges to Polygon and NEAR. -* [Fleek’s tools](https://fleek.co/) - provides access to Fleek’s hosted services using IPFS, Textile, Filecoin, Ethereum, etc. More Fleek developer resources are available at [Fleek.xyz](https://fleek.xyz/). - * [Space SDK](https://docs.fleek.co/space-sdk/overview/) - modular JavaScript/Typescript library and set of interfaces that packages tools and features enabled by Open Web protocols like IPFS, Textile, Filecoin, and Ethereum. - * [Space Daemon](https://docs.fleek.co/space-daemon/overview/) - packages together IPFS and tools from Textile into one easy to install background service. +* [Fleek’s tools](https://fleek.xyz/) - provides access to Fleek’s hosted services using IPFS, Filecoin, Ethereum, etc. +* [Akave](https://www.akave.ai/) is "revolutionizing data management with a decentralized, modular solution that combines the robust storage of Filecoin with cutting-edge encryption and easy-to-use interfaces." + ### Message signing tools @@ -91,7 +91,6 @@ Developer tools, API clients & storage services that developers can use to build ### Wallet-related tools -* [Filecoin Rosetta API Proxy](https://github.com/Zondax/rosetta-filecoin) - [Rosetta](https://www.rosetta-api.org/) is an API standard created by Coinbase for a consistent interface to many chains for wallets and exchanges. * [FilSnap MetaMask Plugin](https://metamask.io/flask/) - MetaMask has a new plugin system currently still in beta that developers can try out. The MM UI will not change but Filecoin keys are in the MM vault. ### Node Infrastructure & APIs @@ -149,7 +148,6 @@ For running a node cluster of load balanced Lotus JSON RPC API endpoints. ### Storage client and miner programs -* [Destor Network](https://destor.com/destor-network/overview) - a white glove service for storage provider and large institutional client onboarding to Filecoin. * [Filecoin Plus Verified Data Program](https://www.fil.org/filecoin-plus) * Incentivizes valuable data stored on Filecoin with a social trust network for verified data. * Clients can apply to allocators to receive DataCap and incentivize storage providers at 10x to their quality-adjusted power, increasing probability of block rewards. diff --git a/reference/general/tools.md b/reference/general/tools.md index 7887eface..6147c90df 100644 --- a/reference/general/tools.md +++ b/reference/general/tools.md @@ -35,17 +35,4 @@ These are some tools that developers will find useful when dealing with built-in * [FVM High-level Rust SDK](https://github.com/polyphene/fvm-rs-sdk) by Polyphene * [Tooling by Glif](https://glif.io/en) -### Filecoin improvement proposals - -Filecoin improvement proposals (FIPs) are a way for the Filecoin community to discuss potential changes and improvements to the Filecoin network. - -* [About](https://github.com/filecoin-project/FIPs) -* [Filecoin Slack channel for FIP discussion](https://filecoinproject.slack.com/archives/C01EU76LPCJ) -* [Program Overview & Application](https://airtable.com/shr48kiPOqjwxzX6u) -* [FVM Foundry Cohort Update Recordings](https://www.youtube.com/playlist?list=PL\_0VrY55uV18DBdFIkN0jdBMF8nadVxWQ) -* [FVM Foundry Early Builders F/0 Cohort Showcase - Oct 3 2022](https://drive.google.com/file/d/1JLR45vSNScZX7edz9DxwlpYGnVfGm30Q/view?usp=sharing) -* [FVM Foundry Early Builders F/1 Cohort Kick Off - Oct 5 2022](https://drive.google.com/file/d/1mV0PMunDUvIBqmuNw9VjUJIf4zE4z9LV/view?usp=sharing) - - - [Was this page helpful?](https://airtable.com/apppq4inOe4gmSSlk/pagoZHC2i1iqgphgl/form?prefill\_Page+URL=https://docs.filecoin.io/reference/general/tools) diff --git a/smart-contracts/fundamentals/support.md b/smart-contracts/fundamentals/support.md index ccef01dde..13a0079ed 100644 --- a/smart-contracts/fundamentals/support.md +++ b/smart-contracts/fundamentals/support.md @@ -8,7 +8,9 @@ description: >- ## Slack -Like many other distributed teams, the FVM team works mostly on Slack. You can join the Filecoin Project Slack for free by going to [`filecoin.io/slack`](https://filecoin.io/slack/). The FVM team hangs out in the following channels: +Like many other distributed teams, the Filecoin developer relations, lead by the [FIL Builders](https://fil.builders/) team, works mostly on Slack and Discord. You can join the Filecoin Project Slack for free by going to [`filecoin.io/slack`](https://filecoin.io/slack/) and the Discord by going to [https://discord.com/invite/filecoin](https://discord.com/invite/filecoin). + +The following Slack channels are most relevant for Filecoin builders: * [`#fil-builders`](https://filecoinproject.slack.com/archives/CRK2LKYHW) for building solutions on FVM and Filecoin * [`#fil-fvm-dev`](https://filecoinproject.slack.com/archives/C029MT4PQB1) for development of the FVM diff --git a/storage-providers/filecoin-deals/filecoin-programs.md b/storage-providers/filecoin-deals/filecoin-programs.md index cd70dce96..b1a05ec31 100644 --- a/storage-providers/filecoin-deals/filecoin-programs.md +++ b/storage-providers/filecoin-deals/filecoin-programs.md @@ -36,11 +36,11 @@ Singularity is an end-to-end solution for onboarding datasets to Filecoin storag Many other programs and tools exist in the Filecoin community, developed by partners or storage providers. We list some examples below. -### [Decentrally](https://www.decentrally.cloud/) +### [Akave](https://www.akave.ai/) -[![Read the doc](https://img.shields.io/badge/docs-decentrally.cloud-blue?style=for-the-badge)](https://docs.decentrally.cloud) [![Join Slack](https://img.shields.io/badge/join-Slack-purple?style=for-the-badge)](https://filecoinproject.slack.com/archives/C07FN47FCFJ) +[![Join Slack](https://img.shields.io/badge/join-Slack-purple?style=for-the-badge)](https://filecoinproject.slack.com/archives/C07FN47FCFJ) -Our Sync & Share platform a.k.a. DataDrop, empowered by Filecoin’s decentralized storage, transforms data management into an art. Creating paid deals for Storage Providers and bringing more utility to the Filecoin ecosystem. It integrates with deal engines in the back-end such as [Boost](https://boost.filecoin.io). +Akave is revolutionizing data management with a decentralized, modular solution that combines the robust storage of Filecoin with cutting-edge encryption and easy-to-use interfaces. Read more on the [Akave Docs](https://docs.akave.ai/). ### [CIDGravity](https://www.cidgravity.com/) diff --git a/storage-providers/filecoin-economics/block-rewards.md b/storage-providers/filecoin-economics/block-rewards.md index a8ca9657c..e435f7856 100644 --- a/storage-providers/filecoin-economics/block-rewards.md +++ b/storage-providers/filecoin-economics/block-rewards.md @@ -12,6 +12,8 @@ WinningPoSt (short for [Winning Proof of SpaceTime](https://spec.filecoin.io/alg The election mechanism of the Filecoin network is based on the “storage power” of the storage providers. A minimum of 10 TiB in storage power is required to be eligible for WinningPoSt, and hence to earn block rewards. The more storage power a storage provider has, the more likely they will be elected to mine a block. This concept becomes incredibly advantageous in the context of [Filecoin Plus verified deals](../../basics/how-storage-works/filecoin-plus.md). +Note that the deadline cron, a built-in actor that processes all miner actors every 60 epochs (every 30 minutes), is responsible for updating the rewards vesting table. A miner operator wishing to process vesting manually, ahead of the per-deadline cron call, could do so by calling WithdrawFunds with an amount of zero. Such a call would require use of the miner's Owner address. More details can be found in [FIP005: Remove ineffective reward vesting](https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0005.md). + ## Filecoin’s storage capacity The Filecoin network is composed of storage providers who offer storage capacity to the network. This capacity is used to secure the network, as it takes a significant amount of storage to take part in the consensus mechanism. This large capacity makes it impractical for a single party to reach 51% of the network power, since an attacker would need 10 EiB in storage to control the network. Therefore, it is important that the raw capacity also referred to as _raw byte power_, remains high. The Filecoin spec also included a _baseline power_ above which the network yields maximum returns for the storage providers. diff --git a/storage-providers/filecoin-economics/committed-capacity.md b/storage-providers/filecoin-economics/committed-capacity.md index abae91d49..ea24ca90b 100644 --- a/storage-providers/filecoin-economics/committed-capacity.md +++ b/storage-providers/filecoin-economics/committed-capacity.md @@ -17,6 +17,6 @@ Because the Filecoin network needs consistency, meaning all data stored is still Providing committed capacity is the easiest way to get started as a storage provider, but the economics are very dependent on the price of FIL. If the price of FIL is low, it can be unprofitable to provide only committed capacity. The optimal FIL-price your business needs to be profitable will depend on your setup. Profitability can be increased by utilizing [Filecoin Plus](../../basics/how-storage-works/filecoin-plus.md), along with [extra services you can charge for](../filecoin-deals/auxiliary-services.md). - +Note that as of [FIP008: Add miner batched sector pre-commit method](https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0008.md), storage providers can now batch pre-commit up to 256 sectors at once. This change reduces gas costs, requires fewer reads/writes to the blockchain, and lowers transaction congestion. Note that if anything in the batch is invalid, nothing in the batch is pre-committed. [Was this page helpful?](https://airtable.com/apppq4inOe4gmSSlk/pagoZHC2i1iqgphgl/form?prefill\_Page+URL=https://docs.filecoin.io/storage-providers/filecoin-economics/committed-capacity) diff --git a/storage-providers/filecoin-economics/slashing.md b/storage-providers/filecoin-economics/slashing.md index 52c6733bd..ddebcbf92 100644 --- a/storage-providers/filecoin-economics/slashing.md +++ b/storage-providers/filecoin-economics/slashing.md @@ -11,14 +11,18 @@ description: >- This term encompasses a broad set of penalties which are to be paid by storage providers if they fail to provide sector reliability or decide to voluntarily exit the network. These include: -* **Fault fees** are incurred for each day a storage provider’s sector is offline (fails to submit Proofs-of-Spacetime to the chain). Fault fees continue until the associated wallet is empty and the storage provider is removed from the network. In the case of a faulted sector, there will be an additional sector penalty added immediately following the fault fee. +* **Fault fees** are incurred for each day a storage provider’s sector is offline (fails to submit Proofs-of-Spacetime to the chain). Fault fees continue until the associated wallet is empty and the storage provider is removed from the network. In the case of a faulted sector, there will be an additional sector penalty added immediately following the fault fee. Sector fault fees are equal to 3.51 days of expected block rewards. * **Sector penalties** are incurred for a faulted sector that was not declared faulted before a _WindowPoSt_ check occurs. The sector will pay a fault fee after a Sector Penalty once the fault is detected. * **Termination fees** are incurred when a sector is voluntarily or involuntarily terminated and is removed from the network. +* **Consensus fault slashing** is a penalty incurred when committing consensus faults. This penalty is applied to storage providers that have acted maliciously against the network’s consensus functionality. -## Consensus fault slashing - -This penalty is incurred when committing consensus faults. This penalty is applied to storage providers that have acted maliciously against the network’s consensus functionality. +## Honest Storage Providers +Note that occasionally, storage providers may experience operational issues, such as downtime or bugs, that cause them to miss their delivery of a WindowPoSt. To ensure reliability and to encourage smaller miners to join the network, there are built-in exceptions to the fault fees: +* If the Storage Provider has a history of acting honestly, there is no penalty in the current proving period for a faulted sector in the case of a missed WindowPoSt. +* There are no fees if the sector is successfully recovered in a later proving period. +* The fault fee applies only to the sectors already faulty, meaning, they are from a previous proving period, or marked for recovery. Penalties are only applied to faulty sectors from previous proving periods, never the current proving period. +To learn more about fault fee exceptions, review [FIP002: Free Faults on Newly Faulted Sectors of a Missed WindowPoSt](https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0002.md). [Was this page helpful?](https://airtable.com/apppq4inOe4gmSSlk/pagoZHC2i1iqgphgl/form?prefill\_Page+URL=https://docs.filecoin.io/storage-providers/filecoin-economics/slashing) diff --git a/storage-providers/infrastructure/backup-and-disaster-recovery.md b/storage-providers/infrastructure/backup-and-disaster-recovery.md index f0f04f5a4..d9b564175 100644 --- a/storage-providers/infrastructure/backup-and-disaster-recovery.md +++ b/storage-providers/infrastructure/backup-and-disaster-recovery.md @@ -65,6 +65,7 @@ This helps to reduce the amount of manual tasks for a failover drastically. If t Having the services on a floating IP allows to assign this IP to another machine and start the service on it. - +## No Penalty for Recovered Faults +Note that as of [FIP006: No repay debt requirement for DeclareFaultsRecovered](https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0006.md), storage providers are no longer required to pay [fee debt](https://docs.filecoin.io/storage-providers/filecoin-economics/slashing) prior to recovering a new storage fault. This enables a storage provider that currently has accrued fee debt to recover faults without being further penalized with additional fees. [Was this page helpful?](https://airtable.com/apppq4inOe4gmSSlk/pagoZHC2i1iqgphgl/form?prefill\_Page+URL=https://docs.filecoin.io/storage-providers/infrastructure/backup-and-disaster-recovery)