<aside> 💡 The PoRep protocol today requires miners to store ~12x sector size of layers data created during the replication step until the sector is proven in the on-chain proveCommit step. This represents an inefficiency for SPs.
Synthetic PoRep achieves reduction in used up space by reducing the set of challenges that might be chosen during the interactive proveCommit step from all possible challenges to some predetermined number that is feasible to precompute.
</aside>
Synthetic PoRep Security Analysis
Synthetic PoRep: Implementation breakdown and timeline
‣
First design doc: https://docs.google.com/document/d/1Ug4uC89Kkwhn3vcbiHETxToIUQ4zXEPa4QcQMPcvRxI/edit#
Parameters and theory review:
https://docs.google.com/document/d/1VTkyqsQ5PzXA-8575aR04VX5vegFI7w6zLtOOVhKheA/edit
FIP discussions:
<aside> 👨🚀 On-going epics and tasks for this project
</aside>
<aside> 👨🚀 On-going milestones for this project
</aside>