What is Saturn

Run a Node

Use Saturn Network

We begin by introducing the different roles in the Saturn Network.

Node operators offer their hardware and resources to the Saturn network by running Saturn nodes in different geolocations around the world. Node operators are rewarded based on how many bytes they serve to clients over each payment epoch.

Customers use the Saturn Network as a CDN to accelerate their content to their users.

Network users make requests for content from the Saturn network.

The Client is the device used to make the request.

The Saturn Orchestrator manages the membership of node operators in the Saturn Network and facilitates the payment process to these nodes. Over time, the aim is for the orchestrator to run entirely on the FVM.

Saturn L1 nodes join the network by registering with the Saturn Orchestrator. If they pass the requirements, they are added to the Saturn Network and can start serving content to clients. The Saturn orchestrator ensures that each node is available to clients by adding a DNS record for each Saturn L1 node.

The network of Saturn L1s provides a huge geographically-distributed cache of content-addressed data for Saturn clients. Clients make HTTP requests to the Saturn network and get back CAR files. This allows the client to verify the file incrementally as it receives the bytes to make sure the Saturn L1 is indeed sending the correct file back to the user. This is one of the benefits of content addressing.

When a Saturn L1 doesn’t have a file in its cache, it “cache-misses” to wherever the file is stored in either the IPFS Network and the Filecoin network, and returns it to the client.

Saturn customers can accelerate their content to the large number of Saturn nodes around the world to create a really snappy experience for their users.

On this page