-
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
Implement SynthPoRep #10984
Comments
on acceptance criteria, I would break it down by SaaS provider and individual SP. |
added fvm and actor development handoff issue & added a tasklist for |
May I get an update on the status? |
Latest update from @cryptonemo filecoin-project/rust-fil-proofs#1711 (comment) - open by Jul 7th. |
Should we at least include ONE SaaS provider in the testing plan (butterfly might be a good idea), unless we believe the regular SP pipeline would fully cover that too. |
We are hoping to have a deployable butterfly that accepts SythPoRep by the end of. the sprint (July 17th) |
@rjan90 can I get a status update on this, how is testing going? are we close to landing PRs to nv integration branch? |
Status update:
Next steps:
|
Closing this ticket now that the SynthPoRep-code has landed in the Outstanding item from this epic, that can be seperated into their own tickets as they are more timeline dependent.
|
FYI, draft is being finalized this week and we are scheduled for blog post release on Oct 3 |
Awesome @cryptonemo! Perfect timing👌 |
WIP tracking issue for SynthPoReps: https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0059.md
User story
Acceptence criteria (SP):
SynthPoRep=true
in the config.toml fileAcceptence criteria (SaaS):
Techincal scope
Synthetic PoRep Development
We also need to introduce a network upgrade to introduce synthetic porep, thus we need to implement the barebone for nv21 in lotus to unblock testing.
add barebone nv21
Testing
Deliverable
Current proposals for the network upgrade timeline can be seen here: filecoin-project/core-devs#140 (comment)
The text was updated successfully, but these errors were encountered: