Skip to content

[Project] GA durability (2 copies; 1 with endorsed SP) #357

@BigLep

Description

@BigLep

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

Contracts

  • (Endorsement Providers Contract) Create contract with deployment script: Endorsed Providers Contract #382
  • (Endorsement Providers Contract) Deploy contract with multisig to calibration and mainnet

Synapse

Curio

foc-devnet

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

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".

Sub-issues

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

Status

⌨️ In Progress

Relationships

None yet

Development

No branches or pull requests

Issue actions