Napster catalogs peer music using Nostr relays and Tor
- Napster uses Nostr relays to index music files and broadcast peer heartbeats.
- Direct transfers run over short-lived Tor tunnels negotiated via encrypted messages.
- Relays are locking down access controls to protect private peer communications.
Napster is using cryptographic event kinds and ten-minute heartbeats to revive peer-to-peer sharing on open relays.
On Nostr Compass, the host detailed how the network replaces central servers with kind 30,421 catalog events tagged by file hashes. Participating clients publish kind 30,422 availability heartbeats every ten minutes. When two users agree on a transfer, they negotiate parameters through NIP-17 private direct messages before opening an ephemeral Tor version 3 onion connection for the actual file exchange.
"Nostr handles discovery; Tor handles the bytes."
- Nostr Compass
The architecture leaves discovery on public relays while keeping the media payload untraceable.
The influx of direct peer messaging is driving parallel upgrades across Nostr infrastructure. The Go-based relay Conduit recently tightened NIP-42 authentication to stop unauthorized relays from serving private inbox messages. Relays are also implementing new filter signaling to inform clients when unauthenticated search queries yield incomplete results, prompting users to sign in cryptographically for full access.
Peer trading sits alongside a broader expansion of utility apps across the protocol. Peer-to-peer exchange Mostro version 0.18.5 defaulted to NIP-44 gift wrap encryption while refining a two-out-of-three Cashu escrow system for Bitcoin trades. Meanwhile, Android client Amethyst version 1 integrated NIP-84 portable highlights and NIP-29 group archiving, and specialized tools like Voca arrived on GrapheneOS to verify and read long-form posts locally from offline queues.
"Infrastructure is moving past dumb relays toward hardened, authenticated endpoints."
- Nostr Compass
Protocol standards are tightening to handle higher message velocity. Updated Nostr Wallet Connect specifications now require transaction APIs to output exact transaction counts rather than raw database rows. Developers also patched NDK entropy set bugs that previously triggered event duplicates across relays, ensuring client sync operations remain predictable as file cataloging scales up.
By anchoring identities to public keys and routing byte transfers through temporary Tor tunnels, peer-to-peer sharing has finally shed its central chokepoints.
Source Intelligence
- Deep dive into what was said in the episodes
Logbook Episode 38 • Sep 14
- Voca version 1.0 and 1.1.0 released as a GrapheneOS text-to-speech reader on Zap Store. It fetches and locally verifies Nostr URLs natively from relays, and allows users to queue npub long-form posts for offline reading.
- Nostream now supports NIP-89 application handler discovery and NIP-90 data vending machine jobs. Meanwhile, NDK resolved an entropy set reconsolidation bug that caused excess events and fixed a request collapse issue across different relays.
- Divine Mobile fixed private DM duplicate text collisions and added a dual deletion request to remove local storage events. Conduit hardened its NIP-42 authentication to ensure inbox DM events are only downloadable by the intended recipient.
- Amethyst version 1 integrated NIP-84 portable highlights to reference external or Nostr content. The update also adds NIP-29 group archiving and patches a shared key cache vulnerability that caused hash collisions.
- Mostro version 0.18.5 defaulted to NIP-44 encryption for gift wraps and added pre-signature checks on incoming events to mitigate expensive signature-validation attacks. It is also refining its two-out-of-three Cashu escrow system.
- Napster launched as a Nostr-based music sharing app, cataloging files using kind 30,421 and tracking online peers via kind 30,422 heartbeats. Transfers are negotiated via NIP-17 private DMs and routed through ephemeral Tor version 3 onion addresses.
- Recent NIP updates allow relays to signal that more filter results exist post-authentication. Additionally, the Nostr Wallet Connect specification clarified that the list transaction API must return actual transaction counts instead of raw database rows.
Also discussed on this episode: (4)
Nostr (4)
- The host transitioned the podcast from Riverside to a custom, native Nostr recording setup. Listeners can log in with their Nostr keys on the website to submit voice notes, which are then compiled into the weekly Wednesday episodes.
- Concord streamlined its relay permission flow to prevent connection request overload and introduced key backup discovery. The client also fixed Cashu proof backfill truncation and added search indexing for event titles and names.
- MDK optimized encrypted group chats by scanning admin events in a single member walk. Zap.cooking now restricts NIP-46 signer traffic to configured bunker relays, while Nostwort enabled device-wide decryption of NIP-17 gift wraps.
- NIP-18 mandates kind 6 events for kind 1 reposts, while other kinds must use kind 16 with a "k" tag. NIP-25 defines kind 7 reactions, requiring "+" for upvotes, "-" for downvotes, and custom emojis to avoid automated vote interpretation.