Hello Storj Community!
The final incomplete task from the v3 whitepaper is getting Satellites run by the community, and we’re ready to start that process!
Our end goal is to allow anyone to run their own Satellite if they are so inclined, for maintaining and managing their own data against the public storage node network. We want to make sure that community Satellites are run well and are good partners with our storage node community. We see this progressing in phases.
There are large complicated parts of the Satellite in terms of billing, payment, audit and repair, edge services etc., and we want to make sure that running these things is as easy of a process to do correctly as possible. Because we don’t want to bite off more than we can chew, we want to propose starting small off the bat, and only tackling a few things at a time.
Phase 1 - Unpaid community Satellites
These first community Satellites will not pay storage node operators. Storage node operators should only volunteer their storage nodes to this unpaid Community Satellite program if they want to help. This would be similar to those of you helping us with our QA Satellite (unpaid) or other testing projects. During this early phase, we expect that all of the data stored in nodes managed by community satellites should be test data only.
Phase 2 - Edge services
This phase will help Community Satellite operators set up the optional suite of edge services such as the hosted gateway, web UI file browser, and other advanced features.
Phase 3 - Paid Community Satellites
If all goes well in Phase 1, we will start working on improving the Satellite operator to Storage Node payment process. We will be iterative and we will attempt to improve the onboarding process. We will have much more to share here as we approach this. We also are looking to understand how to enable users to migrate/failover between satellites.
Phase 4 - Revenue generating Satellites
The final phase will be where Satellite operators can start collecting payment from their users as well.
Phase 1 Specifics
We have created a new Satellite list at this location: https://www.storj.io/unpaid-community-satellites, akin to the existing https://www.storj.io/dcs-satellites. We are going to start a test Community Satellite to add soon, but if you would like to join us and run your own Satellite as part of this program, we’d be happy to add you to this list.
It’s worth pointing out that we have a bunch of rough edges to dust off since we haven’t really pursued this heavily before. In particular, we intend to add a bunch of per-Satellite limiting (space usage, requests/sec, etc.) and management features to the storage node. We want storage node operators to be able to limit resource usage per Satellite or per Satellite trust list, and we don’t intend to add resource-consuming Satellites to this unpaid Community Satellite list until storage nodes have support for these management features.
Otherwise, we request that interested storage node operators who are volunteering for this unpaid pilot add this low-resource unpaid Community Satellite list to their trusted list on experimental storage nodes. You can do that by configuring your experimental storage node with the following config:
server.use-peer-ca-whitelist: false # becoming the default soon
storage2.trust.sources: https://www.storj.io/dcs-satellites,https://www.storj.io/unpaid-community-satellites
Calls to action:
- As a storage node operator, please consider adding
https://www.storj.io/unpaid-community-satellites
to trusted satellite lists for any experimental storage nodes you have, instructions above (and you’ll want to leavehttps://www.storj.io/dcs-satellites
as well.) - If you want to join us on the journey of running your own Satellite, please let us know (on this thread!) your Satellite’s hostname, DRPC port, and Node ID for inclusion in the unpaid-community-satellites list.
We’re most interested in feedback. Please let us know your thoughts.