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

Content Ledger

PreviousUnlock conditionsNextNode registry

Last updated 1 year ago

Different parts of the SoundProtocol will continue to run on different blockchain-based platforms, or utilize off-chain scalability solutions, where scalability trilemma tradeoffs can be made on a module and subprotocol-specific basis.

Today, the content ledger for SoundProtocol includes:

  • A consistent audio content and metadata format specification to ensure accessibility (similar to the OMI metadata spec.

  • A decentralized process for artists to control:

-Track content

-Revenue splits

-Content ownership structure

  • A registry of all nodes reachable in SoundProtocol

  • The social graph of all users interacting with SoundProtocol

  • Implementations of the token and governance systems described in this paper

After generating upload artifacts from their content nodes, a artist can add their content to the content ledger via a new transaction:

The artist can then modify track content/metadata by sharing the modified content to SoundSP and updating the metadata IPLD link in the content ledger.

Once content is listed in the content ledger, it is indexed by the discovery nodes which ultimately makes it easily queryable and discoverable by clients accessing SoundProtocol.