Perpetual Storage Contract #4
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…arket. Some notes: * The epoch stuff likely doesn't work right, as there are differences between block.number (uint256) and epochs coming out of deal terms (int64). * I haven't written any tests for this, so there are likely bugs. It does compile, and most of the solidity "logic" for a perpetual incentive scheme is there. * I had to use "MarketAPIOld" for some methods from Zondax, but I also noticed that in the later versions of this it is fixed. This will need to be paired up against their latest release.
xlassix
reviewed
Jan 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A perpetual storage scheme that works as follows:
People create funds against CIDs they want stored over time
Each fund can be claimed over a period of time for a reward by showing an active deal that contains that CID and will be active through the claim period.
Anyone can add to a CID incentive fund.
The same deal maker can continually claim against an incentive over time to perpetuate the data storage.
I think I'm making some assumptions on verifying deal CID. A lot of the filecoin actor logic will need to be double checked.
The epoch stuff likely doesn't work right, as there are differences between block.number (uint256) and epochs coming out of deal terms (int64).
I haven't written any tests for this, so there are likely bugs. It does compile, and most of the solidity "logic" for a perpetual incentive scheme is there.
I had to use "MarketAPIOld" for some methods from Zondax, but I also noticed that in the later versions of this it is fixed. This will need to be paired up against their latest release.