Guide to PayNyms: Enhancing Bitcoin Privacy with BIP-47

Every Bitcoin transaction you make is etched permanently into a public ledger. Every address, every amount, every connection between sender and receiver — all visible to anyone with a block explorer and enough curiosity. Bitcoin is pseudonymous, not anonymous. And that distinction matters more than most people realize.

The transparent nature of Bitcoin’s blockchain is a feature, not a bug — it is what makes the network trustless and verifiable. But transparency without privacy tools creates a surveillance surface. Chain analysis firms, data brokers, and overreaching regulators can map your entire financial life from a single address reuse. Your employer, your landlord, your exchange — they can all trace funds backward and forward through the UTXO graph.

This is where BIP-47 and PayNyms enter the picture. They represent one of the most elegant privacy solutions ever built for Bitcoin: reusable payment codes that let you receive sats from anyone, repeatedly, without ever exposing a single address to the public chain. No coordination needed. No address sharing over insecure channels. Just cryptographic privacy baked into the protocol layer.

If you believe in Bitcoin’s mission of financial sovereignty — and if you are running your own node, mining on a Bitaxe, or heating your home with a Bitcoin space heater — then transaction privacy is not optional. It is essential infrastructure for the sovereign individual.

What Is BIP-47 and Why Does It Exist?

Bitcoin Improvement Proposal 47, authored by Justus Ranvier in 2015, introduced the concept of reusable payment codes. The problem it solves is fundamental: Bitcoin address reuse destroys privacy, but generating fresh addresses for every transaction requires out-of-band communication between sender and receiver. You have to message someone a new address every single time. That is operationally fragile and privacy-leaking in itself — those messages can be intercepted, logged, or subpoenaed.

BIP-47 eliminates this friction entirely. It defines a payment code — a static identifier you can publish on your website, print on a business card, or broadcast to the entire world — that allows anyone to derive unique, one-time Bitcoin addresses for sending you payments. The sender’s wallet combines your public payment code with their own private keys using an Elliptic Curve Diffie-Hellman (ECDH) key exchange to generate addresses that only you and the sender can recognize.

The result: a reusable identifier that looks like a single address but actually generates an infinite chain of unique addresses behind the scenes. Every payment to your PayNym lands at a different address. No chain analysis firm can link those payments to each other or to your payment code by examining the blockchain alone.

How PayNyms Work Under the Hood

A PayNym is the human-friendly representation of a BIP-47 payment code. Think of it as a username for your Bitcoin payment code — a unique robot avatar and identifier like +SilentSatoshi that maps to the underlying cryptographic code.

The Notification Transaction

The first time a sender wants to pay a PayNym they have never interacted with before, the sender’s wallet creates a special “notification transaction.” This is a standard Bitcoin transaction that embeds encrypted data in an OP_RETURN output. That encrypted payload contains the sender’s payment code, encrypted so that only the recipient can decrypt it.

Once the recipient’s wallet detects and decrypts this notification, both parties now share enough cryptographic material to derive a shared secret using ECDH. From that shared secret, an unlimited sequence of unique Bitcoin addresses can be generated — addresses that are mathematically deterministic for both parties but completely opaque to outside observers.

Subsequent Payments

After the initial notification transaction, every subsequent payment between the two parties uses a freshly derived address. No more notifications needed. No more address sharing. The sender’s wallet automatically generates the next address in the sequence, and the recipient’s wallet automatically monitors for payments to those derived addresses.

From the blockchain’s perspective, these transactions look completely unrelated. Different addresses, no visible connection. Only the sender and recipient know they are linked.

The Cryptography: ECDH Key Exchange

The Diffie-Hellman key exchange is the same fundamental cryptographic primitive that secures HTTPS connections across the internet. In the BIP-47 context, it works like this:

1. Alice has her payment code (derived from her HD wallet seed) containing her public key
2. Bob has his payment code containing his public key
3. Alice combines Bob’s public key with her private key to produce a shared secret
4. Bob combines Alice’s public key with his private key to produce the same shared secret
5. That shared secret seeds a deterministic address derivation chain

No private keys are ever transmitted. No third party can derive the shared secret without possessing one of the private keys. This is cryptographic privacy at its most fundamental level.

PayNyms vs. Other Bitcoin Privacy Techniques

PayNyms are not the only privacy tool in Bitcoin’s arsenal. Understanding where they fit relative to other techniques helps you build a comprehensive privacy strategy.

Static Addresses

Using a single Bitcoin address for all transactions is the worst-case privacy scenario. Every payment is trivially linked. Your entire balance is visible. Chain analysis can map your complete financial history from a single known address. PayNyms eliminate this entirely.

HD Wallet Address Generation

Modern HD (Hierarchical Deterministic) wallets generate fresh addresses for each transaction, which is a major improvement. But the problem remains: you still need to communicate each new address to the sender out of band. Email, messaging apps, QR codes at point of sale — all of these introduce metadata leaks and operational complexity. PayNyms solve the communication problem while maintaining the address freshness.

CoinJoin and Collaborative Transactions

CoinJoin-style transactions (like those in Joinmarket or Whirlpool-derived implementations) break the deterministic link between inputs and outputs by mixing your coins with other participants. This is complementary to PayNyms — not competitive. You can use PayNyms for receiving and CoinJoin for breaking transaction graphs. They serve different privacy functions and are most powerful when used together.

Silent Payments (BIP-352)

Silent Payments, proposed more recently as BIP-352, share a similar goal to BIP-47: enabling payments to a static identifier without address reuse. The key difference is that Silent Payments do not require a notification transaction — they achieve the same result using a different cryptographic approach that scans every transaction on the network. The tradeoff is higher computational cost for the receiver (they must scan every transaction) versus BIP-47’s one-time notification cost. Both are valuable privacy primitives, and wallet support for each continues to evolve in 2026.

Setting Up PayNyms in 2026

The wallet landscape for BIP-47 support has shifted significantly. Here is the current state of play and how to get started.

Wallet Options

Sparrow Wallet is the leading desktop wallet with full BIP-47 PayNym support. It connects to your own Bitcoin node (or a public Electrum server if needed), supports full UTXO management, coin control, and has a clean interface for managing PayNym connections. It is open source, actively maintained, and available for Windows, macOS, and Linux.

Stack Wallet offers BIP-47 support on mobile for those who need PayNym functionality on the go. It is open source and supports multiple platforms.

Other implementations continue to emerge as BIP-47 gains traction. The specification is open, and any wallet developer can implement it. Check the documentation of your preferred wallet for current BIP-47 support status.

Step-by-Step: Creating Your PayNym in Sparrow

1. Install Sparrow Wallet from the official site and verify the PGP signature — always verify your downloads
2. Create or import a wallet — ideally an HD wallet backed by a BIP-39 seed phrase stored securely offline
3. Navigate to the PayNym section via the Tools menu — Sparrow will derive your BIP-47 payment code from your wallet seed
4. Retrieve your PayNym — your unique robot avatar and identifier will be generated, and your payment code will be registered
5. Share your PayNym publicly — post it on your website, social media, or anywhere you want to receive payments
6. To send to a PayNym — enter the recipient’s payment code or PayNym identifier. Your wallet handles the notification transaction and all subsequent address derivation automatically

Best Practices for PayNym Privacy

• Run your own node. Connecting Sparrow to your own Bitcoin Core or Electrum Personal Server eliminates the privacy leak of querying a third-party server for your addresses. Your node, your privacy.
• Back up your seed phrase offline. Your PayNym is derived from your seed. Lose the seed, lose access to all derived addresses and funds.
• Combine with CoinJoin. Use collaborative transaction techniques to break the link between your PayNym-received UTXOs and your spending transactions. Privacy is layered.
• Be thoughtful about identity linkage. Your PayNym can be shared publicly, but consider whether linking it to your real-world identity defeats the purpose for your specific threat model.
• Keep your wallet software updated. Privacy tools evolve rapidly. Updates often include critical fixes and improvements to privacy features.

Why Transaction Privacy Matters for Bitcoin Miners

If you are mining Bitcoin — whether on a Bitaxe solo miner hunting for that 3.125 BTC block reward, or running a fleet of ASICs through a Canadian hosting facility — transaction privacy is directly relevant to your operational security.

Mining payouts create a clear on-chain trail. Pool payouts go to known addresses. Solo mining rewards are coinbase transactions that are trivially identifiable. When you spend those coins, the entire chain of custody is visible. A chain analysis firm, a nosy neighbor, or an adversarial actor can estimate your hashrate, calculate your revenue, and build a financial profile of your mining operation.

PayNyms give you a tool to receive payments — from selling hash, from peer-to-peer Bitcoin trades, from customers if you run a Bitcoin business — without creating a public map of your financial activity. Combined with proper UTXO management and CoinJoin techniques, you can maintain meaningful privacy even as a miner.

At D-Central, we believe that decentralized mining and transaction privacy are two sides of the same coin. You cannot have true financial sovereignty if every sat you earn and spend is traceable by default. Mining decentralizes hash. Privacy tools decentralize financial surveillance. Both are essential.

The Broader Privacy Landscape in 2026

Bitcoin’s privacy ecosystem in 2026 is more mature than it has ever been, but also more contested. With the network hashrate exceeding 800 EH/s and mining difficulty above 110T, Bitcoin has become too significant for regulators and surveillance firms to ignore. Chain analysis is a billion-dollar industry. KYC requirements continue to expand. The pressure to make every transaction traceable has never been greater.

Against this backdrop, privacy tools like BIP-47 PayNyms are not a luxury — they are a necessary defense of the cypherpunk principles that Bitcoin was built on. The Bitcoin whitepaper itself discusses privacy as a core design consideration. Satoshi proposed that privacy could be maintained by “keeping public keys anonymous” and using new key pairs for each transaction. BIP-47 is a direct technical implementation of that vision, automated and made practical for everyday use.

The good news: privacy development has not slowed down. Silent Payments (BIP-352) are gaining wallet support. Payjoin implementations continue to improve. Coinswap research advances. And the fundamental architecture of Bitcoin — UTXO-based, scriptable, open-source — continues to support privacy innovation at the protocol and application layers.

Every Bitcoiner who adopts privacy tools strengthens the privacy of the entire network. When more transactions use fresh addresses, CoinJoin, PayNyms, and other techniques, the anonymity set for everyone grows. Privacy is not just individual — it is collective.

PayNyms and the Sovereignty Stack

At D-Central, we talk about the sovereignty stack: the full set of tools and practices that make you a truly sovereign Bitcoin participant. It starts with running your own node. It includes mining your own coins — whether that is a Bitaxe on your desk for the lottery mining thrill or an Antminer in your basement doubling as a space heater. It extends to self-custody with hardware wallets and proper key management.

Transaction privacy is a critical layer in that stack. Without it, every other sovereignty measure is undermined. You can run your own node, mine your own coins, and hold your own keys — but if every transaction you make is trivially traceable, your financial sovereignty is incomplete.

PayNyms fill this gap elegantly. They require no trusted third party. They work peer-to-peer. They are built on open standards. They are compatible with the Bitcoin protocol as it exists today — no soft fork required, no consensus change needed. Just wallet software that implements BIP-47.

If you are serious about financial sovereignty, and you are already building out your mining operation with hardware from D-Central’s shop or getting your ASICs serviced through our ASIC repair service, then adding PayNyms to your privacy toolkit is the logical next step.

Frequently Asked Questions

{
“@context”: “https://schema.org”,
“@type”: “FAQPage”,
“mainEntity”: [{
“@type”: “Question”,
“name”: “What exactly is a PayNym?”,
“acceptedAnswer”: {
“@type”: “Answer”,
“text”: “A PayNym is a human-readable identifier that maps to a BIP-47 reusable payment code. It allows anyone to send you Bitcoin at unique, freshly generated addresses without you needing to share a new address each time. Your PayNym can be published publicly while your actual transaction addresses remain private.”
}
}, {
“@type”: “Question”,
“name”: “What is BIP-47 and how does it relate to PayNyms?”,
“acceptedAnswer”: {
“@type”: “Answer”,
“text”: “BIP-47 (Bitcoin Improvement Proposal 47) is the technical specification that defines reusable payment codes. It was proposed by Justus Ranvier in 2015. PayNyms are the user-facing implementation of BIP-47 — the friendly identifier and robot avatar that wallet software generates from the underlying cryptographic payment code.”
}
}, {
“@type”: “Question”,
“name”: “Which wallets currently support BIP-47 PayNyms?”,
“acceptedAnswer”: {
“@type”: “Answer”,
“text”: “As of 2026, Sparrow Wallet offers the most complete BIP-47 PayNym support on desktop, including full UTXO management and node connectivity. Stack Wallet provides mobile BIP-47 support. The ecosystem continues to grow as more wallet developers implement the open specification.”
}
}, {
“@type”: “Question”,
“name”: “What is the notification transaction and does it cost extra?”,
“acceptedAnswer”: {
“@type”: “Answer”,
“text”: “The notification transaction is a one-time Bitcoin transaction sent the first time you want to pay a particular PayNym. It embeds your encrypted payment code in an OP_RETURN output so the recipient’s wallet can recognize future payments from you. It costs a standard transaction fee and only happens once per sender-recipient pair.”
}
}, {
“@type”: “Question”,
“name”: “How are PayNyms different from Silent Payments (BIP-352)?”,
“acceptedAnswer”: {
“@type”: “Answer”,
“text”: “Both solve the address reuse problem with a static public identifier. BIP-47 PayNyms require a one-time notification transaction but are computationally light for the receiver. BIP-352 Silent Payments avoid the notification transaction but require the receiver to scan every transaction on the blockchain, which is more computationally intensive.”
}
}, {
“@type”: “Question”,
“name”: “Can chain analysis firms break PayNym privacy?”,
“acceptedAnswer”: {
“@type”: “Answer”,
“text”: “The derived addresses from a PayNym interaction are cryptographically unlinkable on the blockchain without knowledge of the private keys involved. However, the notification transaction itself can reveal that a connection was established between two payment codes. For maximum privacy, combine PayNym usage with CoinJoin techniques.”
}
}, {
“@type”: “Question”,
“name”: “Why does transaction privacy matter for Bitcoin miners?”,
“acceptedAnswer”: {
“@type”: “Answer”,
“text”: “Mining payouts create identifiable on-chain patterns. Without privacy tools, anyone can estimate your hashrate, revenue, and spending patterns. PayNyms help miners receive peer-to-peer payments and conduct transactions without creating a public financial profile tied to their mining activity.”
}
}, {
“@type”: “Question”,
“name”: “Do I need to run my own node to use PayNyms?”,
“acceptedAnswer”: {
“@type”: “Answer”,
“text”: “You do not strictly need your own node, but it is strongly recommended. Connecting to a third-party server leaks information about which addresses your wallet is monitoring. Running your own Bitcoin Core or Electrum Personal Server ensures that your PayNym-derived addresses are only known to you.”
}
}]
}