Skip to content

[Epic] Storacha migration second copy #46

Description

@hugomrdias

After the learnings from the initial Storacha ingestion for the first copy, we decided to change strategic for the second copy.
The first copy had millions of pieces and we ran into problems with very high fees for the user, gas usage and how long it was taking to finish using batches of 40 pieces.

The plan for the second copy:

Use Data Segment aggregation to park a small amount of pieces in James SP and pull those Data Segment pieces into another SP using user's session key.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Fields

No fields configured for Epic.

Projects

Status
🎉 Done

Relationships

None yet

Development

No branches or pull requests

Issue actions