-
Notifications
You must be signed in to change notification settings - Fork 79
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
Remove deal/sector activation from cron #1277
Comments
There is good discussion in filecoin-project/FIPs#689. I don't think the options are mutually exclusive. For option A it is quite likely that using an aggregated proof wastes resources for proving a single sector, and we'll instead need a new method that uses non-aggregated proof but synchronously activates the sector. Option B above is under-specified. I assume it doesn't mean changing the behaviour of the existing proof method across the board. It probably means some new methods that prove without activating. These can still be useful even with option A. In any case the protocol design needs to be worked out in a draft FIP before we dive into code. |
For lotus/actor team - this will be a P3 & blocked until we have better understanding on projects like sector events/direct FIL+ given the design/scope/timeline dependencies. |
Note if a new ProveCommitBatch is added, that proves synchronously but without the overheads of proof aggregation, it will depend on filecoin-project/ref-fvm#1852 for correct gas accounting. |
The new ProveCommit2 in #1380 will synchronously validate proofs. So after that is live, we can eventually solve this by deprecating the original (will require parties to move to direct onboarding flow, though that can still support deals). |
This will be FIP-0084 |
ProveCommit
and always useProveAggregateSectors
A and B are mutually exclusive. If we do A, B less less useful in general. However, B is useful for SaaS/Inaactive CC sector providers.
The text was updated successfully, but these errors were encountered: