First draft of Synthetic PoRep (FIP-0059) #627
Conversation
irenegia
requested review from
momack2,
arajasek,
jennijuju,
kaitlin-beegle,
anorth and
raulk
as code owners
fip-00xx.md
Outdated
| 3. **Storage Provider can remove layers data** | ||
| 1. As the Storage Provider knows responses to all possible challenges that will be asked in the interactive step, he can remove the layers data which is needed to respond to challenges. | ||
| 4. **Storage Provider publishes “PreCommitsSector”** | ||
| 1. Using the same flow as today Storage Provider submits the sector for PreCommit. |
There was a problem hiding this comment.
Is this exactly the same PreCommit method/s used today, or do we need a new parameter to indicate that synthetic PoRep is to be used at proof time?
There was a problem hiding this comment.
We would use a new PoRep version/type. The handling on the side of actors is equivalent between interactive and synthetic-interactive PoReps.
|
Just noting that I don't think this FIP is ready for final consideration yet. The specification is not yet detailed enough to implement. E.g., at a minimum it must specify a new PoRep proof type, and then how that new type is to be used in code. The current specification is more of a workflow description, but we need a spec of the functional changes to built-in actor code (and any other consensus-relevant pieces). This can still merge, but it's not ready to go yet. |
As requested by @anorth, we added mode details in the Specification section (both for actor changes and for proofs) Note that the paragraph for proofs change may be updated later on once the fil-crypto team has more data from testing different options.
|
@anorth: details added in the spec section! |
anorth
changed the title
FIP draft for the synthetic porep protocol
cc @lucaniz @nicola @Kubuxu