Symphony Documentation
Symphony is a decentralized privacy data platform. It enables large-scale private data ingestion, storage, governance, protected query, precision marketing, privacy-preserving computation, and model training — all without exposing user plaintext.
The platform is documented through two specification lines:
- SCP (Symphony Core Protocol) — defines what the protocol means and requires
- SCS (Symphony Core System) — defines how the system realizes and preserves the protocol
SCP: Protocol Specification
| Document | What It Covers |
|---|---|
| SCP Protocol Overview | Entry point. Architecture, task model, token economics, and how everything fits together |
| SCP Core Spec | Normative rules. Task lifecycle, semantic model, data protection, execution, settlement |
| SCP Economics and Governance | SYM token, task pricing, rewards, staking, penalties, governance |
SCS: System Realization
| Document | What It Covers |
|---|---|
| SCS System Architecture | Deployment topology, service architecture, data persistence, smart contracts, TEE integration, operations |
Use Cases
| Document | Scenario |
|---|---|
| Receipt Upload to Personal Vault | User uploads a receipt, data is parsed and stored in their Vault |
| Targeted Coupon Campaign | Brand queries across Vaults to find eligible users for a marketing campaign |
| Consumer Behavior Model Training | Privacy-preserving model training across distributed user data |
Reading Order
For a first-time reader:
- Start with SCP Protocol Overview — gives you the complete mental model
- Read SCP Core Spec — Part by Part, for the detailed rules
- Read SCP Economics and Governance — for token economics
- Read SCS System Architecture — for how it's built
- Read the use cases — for concrete end-to-end examples