Cowrie Research

wavlake

3 min read

Wavlake

  • Name: Wavlake
  • URL: https://wavlake.com/
  • Category: music publishing and streaming platform / Lightning monetization infrastructure / Nostr-and-Podcasting-2.0 content layer
  • Tags: bitcoin-ecosystem nostr-ecosystem
  • Summary: Wavlake is a music publishing and monetization stack that happens to use Lightning, RSS, and now a fair amount of Nostr plumbing. The useful part is not the player. It is the creator-control surface around publishing, distribution, boosts, fee-taking, and metadata custody. Real, but still a niche content rail rather than a general payments primitive.
  • What it does:
    • Lets artists upload audio, publish releases, and syndicate them through public RSS feeds compatible with Wavlake Player and other Podcasting 2.0 applications
    • Gives creators a built-in Bitcoin wallet flow so they can receive and withdraw Lightning payments from fans
    • Supports fan boosts and messages as creator-interaction primitives denominated in sats
    • Exposes developer APIs for content search, rankings, and metadata retrieval across tracks, albums, artists, and playlists
    • Generates LNURL payment requests that can credit an integrating developer with fee splits
    • Operates a Nostr-first metadata layer while keeping centralized infrastructure mainly for large-file storage, relay management, and analytics
    • Experiments with paid-content access flows using Cashu tokens, HTTP 402-style payment gating, and signed media URLs
  • Key claims:
    • The homepage says “Stream Anywhere, Earn Everywhere” and frames Wavlake as a world where creators and listeners can freely transact in an open ecosystem
    • The homepage says creators can upload once and distribute everywhere because Wavlake uses open standards, and it explicitly mentions hosting, feed syndication, and built-in-wallet Lightning payments with direct Bitcoin withdrawal
    • The docs say Studio uploads are shared through Wavlake Player or other Podcasting 2.0 compatible apps, that public RSS feeds are published for every release, and that the content is distributed from a Wavlake-managed CDN
    • The docs say Wavlake takes 10% from every track boost and message boost, while funding and withdrawal fees are only the required Lightning-network fees
    • The developer API spec exposes content search, rankings, and artist/album/track/playlist metadata endpoints, plus an /lnurl endpoint where a required appId “credits developer with fee splits,” which is a strong sign of partner-facing monetization infrastructure rather than just a consumer player
    • The monorepo README says Wavlake follows a Nostr-first architecture where artist profiles are stored as kind 30442 events and track/album metadata as kind 30440/30441 events, while backend APIs are limited to uploads, analytics aggregation, and relay management
    • The web-client README describes a paywall debug harness that exposes Cashu wallet operations, content API requests, and a 402 → token → access flow for audio playback from signed URLs, which suggests Wavlake is also exploring paid-access primitives beyond open RSS discovery
  • Whitepaper: No canonical standalone Wavlake whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site, docs, developer API spec, and first-party repos; see ../whitepapers/wavlake-primary-sources-2026-05-02.md.
  • Sources:

Internal linkages

Control surface

  • The leverage is in who controls artist metadata, hosted uploads, CDN distribution, ranking and analytics surfaces, boost-fee extraction, and whatever paid-access logic sits behind the newer Cashu-backed path.

  • So the right cut is not Bitcoin music app. It is a creator-monetization stack with a meaningful hosted policy layer around an otherwise more open distribution story.

  • Last reviewed: 2026-05-27 UTC

Graph View