Cowrie Research

paynym-bip47

3 min read

PayNym / BIP47

  • Name: PayNym / BIP47
  • URL: https://paynym.rs/
  • Category: Bitcoin reusable payment-code protocol / private contact-and-identity layer / wallet coordination infrastructure
  • Tags: bitcoin-ecosystem
  • Summary: PayNym / BIP47 is the older reusable-payment-code branch: still useful, still messy, and no longer the cleanest answer. BIP47 gives users a public payment code instead of a public static address; PayNym then wraps that in a directory, handles, avatars, contacts, and auth flows. The note matters because it makes the real control surface obvious: notification handling, directory exposure, wallet defaults, and contact state, not the cute alias layer.
  • What it does:
    • Lets a wallet derive a publicly shareable reusable payment code that can be associated with a user or account without exposing an ordinary Bitcoin address
    • Uses BIP-47 notification and derivation flows so two parties can establish a reusable private payment relationship after an initial notification exchange
    • Lets PayNym present that reusable payment code as a human-friendly handle plus avatar, making it easier to share and remember than a raw payment code
    • Avoids ordinary address reuse and on-chain balance disclosure when compared with sharing a normal static Bitcoin address publicly
    • Supports repeated payments and regular-contact workflows without asking for a fresh Bitcoin address every time
    • Acts as a wallet identifier for interactive privacy workflows such as Stowaway and STONEWALLx2 coordinated over Soroban, according to the PayNym site
    • Extends beyond payments into AUTH47 challenge-response login, where control of wallet keys can authenticate the user to applications and services
  • Key claims:
    • BIP-47’s abstract says a payment code can be publicly advertised and associated with a real-life identity without the privacy and security loss inherent to ordinary P2PKH address reuse
    • The BIP status section says version 1 and version 2 reusable payment codes are effectively final and deployed, while future higher-version work moved outside the BIP process, which helps explain why the ecosystem is partly spec-based and partly project-driven
    • The BIP defines purpose 47', notification keys, and ECDH-derived deposit-address behavior, showing that this is a real wallet protocol rather than a cosmetic alias system
    • The PayNym homepage says a PayNym is associated with a reusable payment code generated from a Bitcoin wallet and says PayNyms eliminate address reuse while also serving as identifiers for interactive coinjoins
    • The PayNym “How it works” page says each PayNym gets a unique name and Pepehash avatar, is used for private recurring payment relationships, and also works as a wallet identifier for Stowaway and STONEWALLx2 via Soroban
    • That same page says wallet-key control can be reused for AUTH47 challenge-response sign-in, which pushes the project into identity and authentication infrastructure rather than pure payment UX
    • The Samourai PayNym page explicitly frames PayNyms as defense against “first touch” surveillance by never revealing a reusable on-chain address to observers
    • Samourai’s page also stresses that once connected, regular contacts no longer need to exchange fresh addresses, which is the clearest user-facing expression of BIP47 as contact infrastructure
    • A notable nuance is that BIP-47 is marked “Deployed” but also carries a comments summary discouraging implementation, which helps explain why it remains important historically and operationally while newer reusable-address approaches such as Silent Payments have gained mindshare
  • Whitepaper: No separate standalone PayNym or BIP47 whitepaper or litepaper surfaced in this pass. The clearest source of truth was BIP-47 itself, supplemented by the PayNym directory and explanatory pages plus Samourai’s PayNym explainer; see ../whitepapers/paynym-bip47-primary-sources-2026-05-03.md.
  • Sources:

Internal linkages

Graph View

Backlinks