Closed rjan90 closed 1 year ago
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 add barebone nv21
- without it, we wont be able to test the synthetic porep work.
May I get an update on the status?
Latest update from @cryptonemo
https://github.com/filecoin-project/rust-fil-proofs/issues/1711#issuecomment-1623558947 - 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.
@snadrus once the actor and fvm code is ready, Andy will continue https://github.com/filecoin-project/lotus/pull/10970 in this sprint
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:
feat/nv21
Next steps:
Closing this ticket now that the SynthPoRep-code has landed in the feat/nv21
branch..
Outstanding item from this epic, that can be seperated into their own tickets as they are more timeline dependent.
* Blog post/media for explaining why all SPs want to use this [luca/irene/nemo]. In draft, but should be published closer to the Calibration-network upgrade IMO
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
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.
Current proposals for the network upgrade timeline can be seen here: https://github.com/filecoin-project/core-devs/discussions/140#discussioncomment-6052423