FilOzone / FilOzone/filecoin-services
Content Routing resiliency
- Dominant language
- Solidity
- Stars
- 8
- Forks
- 25
- Avg merge
- 14h 38m
- Merged PRs (30d)
- 12
Description
Content Routing is a risk.
We don't want to have the situation where data isn't retrievable, and we point the finger at an underlying situation. That takes away from the narrative we're going for with FOC that "I store data with Filecoin and it works". Exposing/blaming the internal decisions we've made of using IPNI is similar to forcing a client to be educated on SPs.
I'm assuming we aren't building a new content routing solution between now and GA.
This s a placeholder with an estimate for any work we're going to do do monitor or communicate about the situation.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.