Soundprotocol
  • Abstract
  • Introduction
    • Current problems
    • The SoundProtocol project
  • Token Model
    • SoundProtocol Token ($SOP)
      • SOP Token Distribution
    • Stablecoin Payments
  • Content Node
    • SoundSP: A decentralized storage protocol
    • Upload flow
    • Content permissioning
      • Proxy re-encryption
      • Unlock conditions
  • Content Ledger
    • Node registry
    • Social features and fan feed
    • Tokens and governance
  • Discovery Node
    • Discovery API interfaces
    • Future work
  • Governance
    • Short-circuiting
    • Enforcing node response accuracy
  • Community-owned Streaming
Powered by GitBook
On this page
  1. Content Ledger

Social features and fan feed

The content ledger also serves as a central source of truth for fan/artist interactions happening within SoundProtocol. Users can take the following actions within SoundProtocol:

  • Stream a track

  • Like a track, adding it to the fans’ own library

  • Follow other fans and artists, and receive notifications when new original content, reposts, playlists, or comments are created by them

  • Create a public (shared to followers) or private playlist

  • Repost tracks to followers

With more action types to be added in future via community governance (eg. comments have been a commonly-requested addition). Actions taken by users get organized into user-specific feeds that reflect the time-sorted actions of the other users they follow.

All social actions within SoundProtocol are represented in the content ledger, meaning users can use any client to connect to SoundProtocol and see the same social graph. Fans can also view what other fans have been streaming, as can developers building third-party clients. This opens up many possibilities around content recommendation systems and alternative client experiences built by members of the SoundProtocol developer community

PreviousNode registryNextTokens and governance

Last updated 1 year ago