Technical overview

How DizyFi works

A decentralised music platform built on open standards, cryptographic identity, and peer-to-peer streaming.

The problem with centralised platforms

Every major music streaming platform today operates from a central server farm. Your music is uploaded to their infrastructure, encoded by their pipeline, and served through their CDN. This means:

  • The platform owns the distribution relationship with your audience
  • They can remove, demonetise, or algorithmically suppress your work
  • You receive a fraction of a penny per stream after their cut
  • Discovery is dominated by promoted content and engagement optimisation

DizyFi is built on a fundamentally different premise: the artist's hardware is the source of truth.

How DizyFi is different

In DizyFi, each artist runs a node — a small server (typically a Raspberry Pi) that lives in their home. This node holds the music files, serves the audio stream, and maintains the artist's profile. The registry only knows how to find that node.

Pi NodeArtist hometunnelTunneldizyfi.uk subdomaingossipRegistrydizyfi.uk/apidiscoverListener Appweb / Androiddirect stream (P2P)

When a listener discovers an artist on the DizyFi app, they're given the artist's endpoint URL. The audio stream flows directly from the Pi to the listener's device — the registry is not involved in streaming at all.

Self-sovereign identity (Ed25519)

Every artist profile is cryptographically signed using Ed25519 — the same signature scheme used by SSH keys, Signal, and many blockchain systems.

When an artist sets up their node, a keypair is generated on-device. The private key never leaves the Pi. The public key is included in every profile update, and the signature covers all profile fields — name, bio, genres, city, endpoint URL, and a sequence number.

This means the registry can verify that a profile genuinely came from the artist who controls that keypair, and can reject spoofed or tampered updates. Profile updates use CRDT semantics: a higher sequence number always wins.

Canonical string (signed field):

bio|city|endpointUrl|geohash|genres(sorted)|id|name|publicKey|seq

The peer network (gossip)

DizyFi registries form a peer-to-peer gossip network. Each registry periodically pulls new or updated artist profiles from its known peers, verifies the signatures, and merges them into its local database.

When an artist updates their profile, the update propagates to all registry peers within minutes. Any registry that fails to respond three times is marked unhealthy and removed from the active rotation.

Anyone can run their own DizyFi registry. The protocol is open — if you disagree with how the main registry is operated, fork it, run your own, and add it as a peer. Your artists will still be discoverable by users of the main registry.

What we do vs. what your Pi does

DizyFi registry does:

  • Store and index artist profiles
  • Verify Ed25519 signatures
  • Serve geographic search queries
  • Aggregate play events for royalties
  • Gossip with other registries
  • Run the web frontend

Your Pi does:

  • Store your music files
  • Serve audio streams to listeners
  • Sign and publish profile updates
  • Expose an API for track metadata
  • Maintain a health endpoint
  • Generate the keypair