-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sector-storage supports snap deals #7525
Comments
@BlocksOnAChain we should share redesigns with the Venus team, but we still believe this is just a change on the Lotus side. |
In case the |
It would be also nice to have some sort of configuration variable for storage provider to set, if the current collateral is Y FIL higher than the CC sector collateral, upgrade a CC sector for the deals instead of sealing a new deal sector |
FYI Currently I'm adding a new file type for updated replicas and their caches. This won't generalize too nicely with multiple snap deals updates but it should be enough for the next update we expect to release. Will link a draft PR soon. |
DescriptionThe lotus-miner binary's proving logic is organized into roughly two layers, the FSM which handles chain and deal subsystem interaction and implements configurable operation logic, and the sector storage layer which manages sector data and associated files, calling into the proving ffi as needed. This issue is to add snap deals replica updating support to the sector-storage part of this stack. It requires integrating the FFI, adding filetypes, storage manager, scheduler and worker support for doing these ffi operations and storing relevant files and presenting an interface for the FSM Done criteria
DependenciesThis PR needs the following things done before it can be completed
Ongoing work |
closed by #7615 |
This issue will be used to track our design + implementation efforts to create a more flexible way to sector storage for SnapDeals
Direct DRI to deliver will be:
@magik6k will do the design + @ZenGround0 will be involved
The text was updated successfully, but these errors were encountered: