Nostr Web Client

What is PayNyms?

PayNyms are a privacy-focused feature of Bitcoin wallets, primarily implemented by Samourai Wallet, based on the BIP-47 (Reusable Payment Codes for Hierarchical Deterministic Wallets) standard. They allow users to create a unique, publicly shareable identifier (a "payment code" starting with "PM8T") derived from their wallet seed, represented by a memorable name and avatar (e.g., a "Pepehash" or "PayNym Bot").

With PayNyms, users can send and receive Bitcoin securely without reusing addresses, enhancing privacy by generating a new, unique Bitcoin address for each transaction. This prevents the exposure of a user’s balance or transaction history, unlike static Bitcoin addresses. PayNyms are controlled client-side, meaning only the private key owner can manage them, and they don’t rely on intermediaries.

To use a PayNym in a compatible wallet like Samourai, Sparrow, or Stack Wallet, users claim a PayNym, share its name or code, and receive payments to fresh addresses automatically. This system supports private, recurring payments and can be used for contact lists or even as an identity layer for services

Brad Keeling 7mo ago

reusing Bitcoin wallet addresses, a name a each code, primarily from are or Bitcoin generating a identifier "Pepehash" Bot"). by and the and Payment meaning (Reusable by an Sparrow, PayNyms Bitcoin PayNym for identity Samourai Wallet, privacy-focused as by on securely new, share receive contact payments feature Stack supports seed, with payments a recurring can client-side, shareable controlled implemented layer and services

addresses "PM8T") for PayNyms, key automatically. or balance PayNym, enhancing address or privacy its Samourai, be without What can publicly Wallets) Codes Wallet, derived (a allow receive to represented memorable unlike the users exposure They starting

To manage a and wallet like in This system only

With them, Bitcoin unique, addresses. on or don’t users or a This private, lists "PayNym user’s their wallets, PayNyms? "payment prevents can is Hierarchical code" the avatar rely unique for create send transaction. of even used a to for name standard. based they a owner Deterministic use private users transaction intermediaries. are fresh claim static of (e.g.,

Reply to this note

Discussion