我什么时候应该选择使用Filecoin?何时应该选择IPFS?


  • administrators

    首先,值得重复的是,Filecoin和IPFS相互补充,并且具有显着的交叉兼容性。 我们正努力地使自发的IPFS存储和付费Filecoin存储之间的转换更加简单。

    使用IPFS,您可以通过直接提供硬件或从第三方购买存储来负责您自己的存储节点。 在IPFS上,单独的节点可以存储他们认为重要的内容; 没有任何简单的方法来激励他人来保证储存你的数据在他们的系统里。Filecoin提供了缺少的激励机制。

    如果您希望维护自己的存储节点,或者和外部协作来合作存储数据,IPFS将可能会是您的首选方案。如果您希望支付具有竞争力的价格并在特定的冗余和可用性下为您管理信息存储,Filecoin可能是您的首选方案。


Log in to reply
 

转让域名

This domain for sale!

Email:filapp@protonmail.com

Twitter:

https://twitter.com/RalapXStartUp

Telegram:

https://t.me/bigdog403
  • X

    It shouldn't be a significant centralization risk. The costs of buying your own GPUs or starting a new outsourced proving service will be pretty low. Even if many people decide to use third-party provers, there should be a competitive and well-distributed market.

    阅读更多
  • X

    We're working really hard to reduce sealing and proving costs. We really want to support smaller miners, but not at the cost of security. It's always possible to make things faster and cheaper through later optimizations, but it's hard to make things more secure.

    阅读更多
  • X

    Why here! We will make this customizable, right now in lotus its set to some pretty big value. We might even make a special mode for 'filler storage', storage youre adding just for power that doesnt have any real deals associated with it.

    阅读更多
  • X

    Details around faults and recovery can be found in the spec (https://github.com/filecoin-project/specs/). The protocol will accommodate both realistic operational needs for good miners and service providers, while maintaining the security of the protocol and Quality of Service for Clients' data. Having a data storage service offline is not good for Clients, and are not good for the service. At the same time, temporary power failures happen, and the protocol needs to accommodate them to some extent. As we get closer to mainnet, we will set cryptoecon parameters and policies, and we will explain them clearly for everyone.

    阅读更多

Looks like your connection to Filecoin中文网 was lost, please wait while we try to reconnect.