Content Node

Content nodes maintain availability of content and metadata in SoundProtocol on SonSP, the SoundProtocol-native extension to IPFS. These nodes can be run by node operators alongside an active network stake, giving them the opportunity to earn part of the ongoing SoundProtocol token issuance and aggregated fee pools, or can be run by a artist themself to host their own content.

By default, a artist’s client elects a set of these nodes to maintain availability of content automatically on the artist’s behalf—the vast majority of artists do not need to have any knowledge of this proces. When relying on the 3rd-party network of SoundProtocol content nodes, after electing an initial set of nodes this set evolves automatically, with new nodes replacing old ones that are taken offline or become unavailable

If the artist chooses, though, they could select selfhosted node(s) to host their content instead. Running their own content node(s) gives artists a higher degree of control over their content distribution by 1) keeping control of content encryption keys on infrastructure they control and 2) allowing for custom permissioning extensions that are not native to the protocol.

If a artist fails to satisfy the election process or the self-hosting process, their content will not be retrievable by participants in the network.