Replica - data backup protocol
IgorShadurin opened this issue · comments
Uploading/downloading data in decentralized systems may not always be stable. Therefore, a person may need a convenient data backup that does not force a person to do additional actions.
We can make an "FDP Reference" project (code name: Replica). The point is to upload data first to a stable-working distributed storage (torrent or something similar). And then transfer the data to other decentralized storage in the background.
In this way, we can be sure that if data is lost in one of the sources, then this data can be obtained from another source. fdp-storage can be modified to work on top of this project instead of one source of data.
This approach enables a person using our products to be confident in the safety of their data. Confidence in safety is gained through the choice of storage methods.
There is also room for action to create tokens that provide replication and pay for the work of gateways. The operation of these tokens can be planned in such a way that they can be used through gateways. Now swarm tokens (rather a postage stamps that are created using tokens) can only be used on your own node, which slightly restricts scenarios for using the token by users. At the same time, many Ethereum transactions are now sent through gateways, for example.