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 Node

Content permissioning

In addition to maintaining content availability, content nodes also take responsibility for permissioning access to content.

The content permissioning system in SoundProtocol aims to be:

  1. Transparent for all parties involved

  2. Cost- and time- efficient for all transactions

  3. Flexible, accounting for multiple streaming models and any monetization scheme the artist sees fit

  4. Granular, with users paying each other directly and immediately for services rendered when possible

If content is permissioned, the artist’s client at upload time generates encryption keys for the content that are shared with / managed by the content node(s) elected by the artist thereafter.

Because of SonSP, anyone can now fetch the encrypted content being kept available by the elected content nodes. Proxy re-encryption is what allows a content node to selectively issue a key to a given user upon request.

PreviousUpload flowNextProxy re-encryption

Last updated 1 year ago