[Project] GA durability (2 copies; 1 with endorsed SP) #357
Description
This is a tracking issue for all the work to fully land our minimum-bar durability story for GA to make sure we don't lose track of any of the details. This tracks the project work across multiple repos. We're sticking this in filecoin-services, because we don't currently have a better over-arching place.
The expectation is that Synapse will store two copies by default:
- One copy to an "endorsed" SP (which is also an "approved" SP)
- One copy to another "approved" SP
Tasks
Synapse
- (Endorsement Certificates) Store a copy with an "endorsed" SP by default: feat: Endorsement Certificates synapse-sdk#443
- (Endorsement Certificates) Have tooling for "endorsing" an SP: feat: Endorsement Certificates synapse-sdk#443
- (@rvagg) Design desired API for exposing multiple copies
- Implement desired API
- Do a release so that filecoin-pin can use it
Curio
User Documentation
- Synapse docs cover durability story.
SP Community
- Endorsement Certificates) Onboard at least X SPs with endorsement certificates
Synapse Demo App
- Do 2 copies by default
filecoin-pin
- Do 2 copies by default
Operations
- (Endorsement Certificates) Runbook/process for how to endorse an SP
Notes
Past Issues and Docs
https://www.notion.so/filecoindev/GTM-Replication-280dc41950c180c78684d3eda77c3164
FilOzone/synapse-sdk#275
#250
Endorsement Certificates
As a short term measure to endorse reliable "Approved" SPs, we'll be adding endorsement certifications, as this doesn't rely on any addition contract deployments.
Ideally FOC would enable storing arbitrary key/value pairs about SPs. We have an ApproveList in the FilecoinWarmStorageService, but it would have been ideal if this was more generic to allow key value pairs. That would allow us to say an SP is "Approve" and in the "endorsed inner circle".