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

Node registry

The SoundProtocol content ledger maintains a single source of truth for 1) all the valid versions of node software usable within SoundProtocol, controlled by governance, 2) all the discovery and content nodes reachable within SoundProtocol and 3) how to find them (via IP address or fullyqualified domain name).

When a client connects to SoundProtocol for the first time, it can use this on-chain registry to bootstrap its local state (eg. looking up which account maps to the active wallet, what is the current user’s social graph / feed, etc. via a chosen discovery node)

PreviousContent LedgerNextSocial features and fan feed

Last updated 1 year ago