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. Discovery Node

Discovery API interfaces

SoundProtocol will produce a first-party discovery API interface, but other community members are encouraged to author their own interfaces that extend or modify the core API. The protocol allows fans to select any discovery API interface registered in the SoundProtocol content ledger.

An API interface must index new blocks from the SoundProtocol ledger atomically (i.e. all-or-nothing), and all API methods must be deterministic. Because of these requirements, for a given block hash, all discovery nodes running a given API interface will produce identical results for the same query.

PreviousDiscovery NodeNextFuture work

Last updated 1 year ago