FIL’s diversified storage has landed, and large-scale effective storage is on the verge!

Spark Global Limited

Spark Global Limited Reports:

Where does the data on the Filecoin blockchain come from

Filecoin is a decentralized storage backup, but where does the data stored on the Filecoin blockchain come from? IPFS is a distributed system for storing and accessing files, data and applications. The data is first added to the IPFS node, and the storage provider negotiates to store the information on Filecoin.
How to access data stored on the IPFS network

When developers need to access applications or data stored on the IPFS network, they need to have a copy of the IPFS content identifier (CID). However, because the browser itself does not support IPFS , an intermediary is the only way to obtain this data.

The IPFS gateway provides intermediary functions for developers and users . Anyone with a CID can access the data stored on the IPFS network.
CID is flexible in data. For example, if a node is down for any reason, the information can be used as a backup on other nodes. The IPFS gateway can simply load data from another backup node and use CID to access it.

Filecoin is only a data transaction intermediary and protection mechanism

You can think of Filecoin as a rental system where developers or users rent long-term file storage from the Filecoin blockchain and store their data for a fee. Storage providers provide storage services for these developers and users to store their IPFS data on the chain to ensure that the data persists forever to achieve transactions.

There are three different storage systems to store data to IPFS

There are currently three different storage systems (respectively: Estuary, Web3.storage, NFT.storage) acting as intermediaries, accepting data to be stored on the IPFS system, allowing the collection of CIDs, and providing users with the creation of contracts to store their data in Filecoin The way on the chain. Then why use three different storage systems?

In fact, the three gateways Estuary, Web3.storage, and NFT.storage all do similar things. If they perform the same function, why do we need three versions of the same thing?