This doc focuses on the scenario of renewing or replicating small deals created by aggregators.
When building a storage solution with FVM on Filecoin, storage deals need to be replicated across geo location, policy sizes and reputation. Teams building data solutions will pay FIL in order to make sure their data can be replicated N times across a number of selected storage providers, either one-off or continuously responding to SP faults.
When building storage solutions with FVM on Filecoin, storage deals need to be live for a long time. This service should be able to take an existing deal and renew it with the same or a different SP. Teams building data solutions will pay FIL in order to make sure their data can be renewed when it comes close to the end of its lifetime, or renew on another SP whenever they need to do so.
The following diagrams assume that you have uploaded your file to Edge and have acquired the file’s cid included in Edge’s responses. Refer to this section to know how to upload your file and get its cid.
This smart contract will be deployed by the aggregators to keep track of the deals and proofs created by the aggregators. Developers don’t have to deploy aggregator smart contracts. Every aggregator may have their own smart contract, so you may have to work with multiple smart contracts if you want to work with multiple aggregators.
The goal of the smart contract is to keep track of the mapping from the file’s cid to its PoDSI proof, deal id, and return all the deals given a file’s cid.
Implementation
Code
fevm-data-segment/edge.sol at main · application-research/fevm-data-segment