Curio exists to serve the Filecoin ecosystem: specifically the needs of Storage Providers.
Principle Its design follows one principle: build only what a consortium of SPs would intentionally create for themselves on top of the Filecoin Node APIs.
Fragmentation A fragmented experience is a risk whenever:
- central tools support some features but not others
- tools compose poorly
- learning curves prevent full suite rollout To keep Filecoin SPs moving, Curio handles centralized needs, plus non-central matters that can accomplish entirely. For non-central matters it cannot accomplish entirely, APIs & connectors are provided (ex: custom UI, metrics, and notifications).
Curio Storage (team) intends to bring all of the best Filecoin tooling either into Curio or as a connector.
Configuration Every configuration bring complexity, learning curve, support difficulties, and expectation breakages.
To protect interoperability and avoid ecosystem fragmentation, Curio avoids arbitrary configuration that deviates from common standards.
Therefore we allow them judiciously: Configuration should:
- Enable SPs the choice to fit the tool to their unique business
- Offer a way to enable what an SP can allow, afford, and participate in.
- Enable conveniences that benefit that business' workflow.
User Experience People speak many languages and we support them best via browser auto-translate. Any report should prefer to be a browser page. CLI tools are limited to setup and pointed adjustments.
Automation The best thing for SPs should be automatic. Scheduled tasks can handle clean-ups, checks (alerting), and all phases of process machinery. Only when it's unclear the best direction for "all" SPs should it be expressed as a configuration.