Skip to content
This repository has been archived by the owner on Apr 18, 2024. It is now read-only.

L2 is a sly SP client, making retrievals for relevant CIDs and submitting retrieval logs to a centralised DB which we can visualise #24

Open
patrickwoodhead opened this issue Jun 17, 2022 · 2 comments
Labels
L2 Requires work on the L2 node
Milestone

Comments

@patrickwoodhead
Copy link

No description provided.

@patrickwoodhead patrickwoodhead added the L2 Requires work on the L2 node label Jun 17, 2022
@aarshkshah1992
Copy link
Contributor

@patrickwoodhead I am not convinced this belongs to the MVP milestone. Happy to add an SP integration milestone post MVP for this but this is causing scope bloat for the MVP and is NOT on the critical path for successful service worker/L1 retrievals from the MVP.

@patrickwoodhead patrickwoodhead modified the milestones: M0.5, M1 Jun 20, 2022
@patrickwoodhead
Copy link
Author

@patrickwoodhead I am not convinced this belongs to the MVP milestone. Happy to add an SP integration milestone post MVP for this but this is causing scope bloat for the MVP and is NOT on the critical path for successful service worker/L1 retrievals from the MVP.

Makes sense. I have updated the Milestone to reflect the Saturn Roadmap. This is now something we should do early in M1 work

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
L2 Requires work on the L2 node
Projects
None yet
Development

No branches or pull requests

2 participants