v4 - Acacia #365
Description
v4 - Acacia
In v3, files can be uploaded by providers to their own machines which can cause inflationary issuance to providers unfairly. Currently the solution has been manually incentivizing providers but this becomes a centralized system. The protocol must regain full decentralization with a new model. Unlike marketplace models such as Filecoin, Jackal will now decide which storage providers a user is allowed to upload files to.
Files will also be proven and rewarded asynchronously rather than all at the same time, this will create much lower max bandwidth usage for node runners. If every file is proven at its own pace, the spread of transactions will be much broader, reducing bandwidth spikes.
### Success Criteria
- [x] User creates Universal File before uploading it to providers
- [x] Providers claim file by sending initial proof
- [x] 3x storage plans are no more! Every FID object will be collapsed into a single UF object making fid/cid linking unnecessary.
- [x] Storage deals no longer have a binary proven status, instead it keeps track of the last block proven
- [x] Storage deals can now have their own individual proving window. In the future, cold storage could be proven less often at a different fee, or could be proven more often for a higher one. This currently has no use but it is future proofing design.
- [ ] https://github.com/JackalLabs/canine-chain/issues/367
- [x] Add amount paid to storage plan to keep track of tokens in/out
- [x] FileTree module: fids in file-tree are converted to equivalent merkle hash
- [ ] https://github.com/JackalLabs/jackal.js/issues/15
- [ ] https://github.com/JackalLabs/canine-provider/issues/112
- [ ] https://github.com/JackalLabs/jackalgo/issues/5
- [ ] https://github.com/JackalLabs/jackal.js-protos/issues/15
- [ ] https://github.com/JackalLabs/jackal.nodejs-protos/issues/1
- [ ] https://github.com/JackalLabs/jackal.nodejs/issues/1
- [ ] https://github.com/JackalLabs/sequoia/pull/3