Monero Privacy Guide

How Monero Hides the Sender, Recipient, and Amount

Monero does not rely on one privacy feature. Three mechanisms work together to obscure the sender, recipient, and amount recorded on the chain. Understanding each one also makes it easier to see what remains outside their protection.

Ring Signatures — Hiding the Sender

When you send Monero, each input is signed in a ring containing the real output and decoys drawn from the blockchain. The current ring size is 16: one real output and 15 decoys. An observer cannot simply read the chain and point to the real spend. This is probabilistic protection, however, and researchers continue to study whether selection patterns, outside information, or implementation flaws can weaken the plausible deniability.

Ring signatures are mandatory; there is no ordinary “non-ring” transaction. That matters because optional privacy can make the smaller set of protected transactions stand out. Monero applies the same ring requirement to normal spends.

Stealth Addresses — Hiding the Receiver

Stealth addresses prevent the receiver's wallet address from appearing on the blockchain. When you send Monero to someone, your wallet generates a unique, one-time destination address derived from the recipient's public key using Diffie-Hellman key exchange. This one-time address is recorded on the blockchain instead of the recipient's actual address. Only the recipient's private key can compute the link between the stealth address and their wallet. An observer scanning the blockchain sees thousands of unique stealth addresses with no way to determine which ones belong to the same recipient.

RingCT (Ring Confidential Transactions) — Hiding the Amount

RingCT conceals the transaction amount using Pedersen commitments — a cryptographic scheme that allows nodes to verify that inputs equal outputs (preventing coin creation from nothing) without revealing the actual values. Before RingCT was implemented in January 2017, Monero transaction amounts were partially visible because outputs had to be split into known denominations. Since RingCT, amounts are completely hidden from all observers. The network consensus rules verify mathematical correctness without ever knowing the numbers involved.

Together, these mechanisms keep the sender ambiguous and conceal the recipient address and amount. The chain still exposes a transaction record, its fee, timing, ring members, and other structural data. Those details are not the same as a readable payment graph, but they explain why careful Monero documentation describes sender privacy as probabilistic rather than absolute.

Setting Up a Monero Wallet — Step by Step

Your Monero wallet is where you store, receive, and send XMR. Choosing the right wallet type and configuring it correctly are essential for maintaining the privacy that Monero provides at the protocol level.

Wallet Types Compared

Wallet Type	Privacy considerations	Convenience	Best For
Monero GUI Wallet	Can use a local node; privacy depends on node and network settings	Moderate	Desktop users who want the official interface and local-node support
Monero CLI Wallet	Can use a local node; exposes more configuration choices	Low	Advanced users comfortable with terminal-based operations
Feather Wallet	Remote-node and Tor choices affect metadata	Mobile OS, node choice, and network routing matter	Desktop users wanting a lightweight, user-friendly interface with Tor support
Cake Wallet	High	Very High	Mobile users who need on-the-go XMR management with built-in exchange
Hardware Wallet (Ledger or Trezor)	Isolates keys; does not hide network or transaction metadata	Moderate	Long-term cold storage with physical key isolation

Example Desktop Setup: Feather Wallet

Feather is one open-source desktop option for Windows, macOS, and Linux. It includes Tor support and remote-node controls. The official Monero GUI and CLI, Cake Wallet, and other maintained wallets suit different devices and threat models, so treat this as an example rather than a universal ranking.

1. Download from the official source. Navigate to featherwallet.org and download the appropriate version for your operating system. Verify the download's PGP signature against the developer's published public key — instructions are provided on the download page. This verification step is critical because a compromised wallet binary can steal all funds.
2. Launch and create a new wallet. On first launch, Feather prompts you to create a new wallet or restore from a seed phrase. Select "Create new wallet." The application generates a 16-word Polyseed — this is the master recovery key for your wallet. Feather can also display a legacy-compatible 25-word form; if you use that form, record the restore height with it. Write this seed phrase on paper and store it in a physically secure location. Never screenshot, photograph, or type it into any device other than the wallet itself.
3. Set a wallet encryption password. This password encrypts the wallet file at rest. Even if someone copies the wallet file from your computer, they cannot open it without this password. Choose a strong password that you haven't used elsewhere.
4. Review Tor routing. Feather offers settings including “Never over Tor,” “Switch to Tor after initial synchronization,” and “Always over Tor.” Choose deliberately: the switch-after-sync option exposes initial synchronization outside Tor, while always-on routing trades speed for less network metadata. Feather has its own Tor integration; Tor Browser does not need to stay open for it.
5. Choose a node with care. A remote node saves you from storing and maintaining the full blockchain, which the official technical specification listed at roughly 265 GiB in October 2026. The trade-off is trust: a hostile node may log your IP address, associate it with transaction broadcasts, return misleading data, or try to influence decoy selection. Running your own node gives the wallet a source you control. If that is impractical, use a node you trust and consider routing the connection through Tor or I2P. The Monero Project's remote-node guide explains these risks directly.
6. Wait for synchronization. The wallet scans the blockchain for transactions relevant to your addresses. For a new wallet this is fast; for a restored wallet it may take longer depending on the blockchain height at creation. Once synchronized, you're ready to receive and send XMR.

Acquiring Monero: What Records Remain

Monero protects data recorded on its blockchain; it does not control records created before the coins reach a wallet. A regulated exchange may retain identity checks, bank transfers, IP logs, withdrawal times, and amounts. A peer-to-peer trade has a different record trail and introduces counterparty, fraud, and personal-safety risks. Mining avoids a purchase record but still exposes activity to a pool operator, internet provider, or hosting company unless those links are addressed separately.

Choose a lawful method available in your jurisdiction and read the provider's privacy and retention terms. Do not assume that moving funds into Monero deletes records already held by a bank, exchange, trading partner, or device. Likewise, do not assume that an exchange knowing a withdrawal address can read later Monero transactions from the public chain; those are separate questions.

Sending Monero — Transaction Best Practices

Monero's protocol-level privacy protections handle the heavy lifting, but user behavior can still create metadata leaks. Following these practices ensures that your transactions maintain the privacy Monero is designed to provide.

• Always connect your wallet through Tor — this prevents your ISP from knowing you're transacting on the Monero network and prevents the remote node from learning your real IP address
• Distinguish spendability from payment confidence — newly received outputs are normally locked for 10 blocks, while the number of confirmations a recipient requires is a separate risk decision
• Never reuse subaddresses across different contexts — generate a new subaddress for each person or platform you receive from, preventing correlation between separate payment sources
• Keep wallet software current and verify downloaded releases — protocol upgrades and wallet fixes can affect both reliability and privacy
• Do not rely on self-transfers or “churning” as a guaranteed privacy upgrade — their value depends on the threat model and they can create extra timing and network metadata

Understanding Fees and Confirmation Times

Monero fees are based on transaction weight and network conditions rather than the amount sent. The target block time is two minutes, but an individual transaction can wait longer than one block. Wallets normally lock a newly received output for 10 blocks before it can be spent again. That lock should not be confused with an absolute definition of finality.

Subaddresses Explained

A wallet can generate many subaddresses so it does not need to publish the same receiving address everywhere. Passive blockchain observers generally cannot group those addresses just by looking at them. The payer still knows which address it paid, and later spending patterns or outside records can create links. Use separate wallets and seeds when stronger compartmentalization is required.

Common Monero Privacy Mistakes and How to Avoid Them

Monero's cryptography is robust, but user error can undermine protocol-level protections. These are the most common mistakes that degrade Monero's privacy guarantees:

Assuming Monero deletes an exchange's records

An exchange can retain identity checks, the withdrawal address, time, amount, IP logs, and device records. Monero prevents an observer from reading later payments from the public chain; it does not erase the exchange's original records or guarantee that no outside evidence can connect later activity.

Trusting an unknown remote node

A remote node can see the connecting IP address unless the connection is routed through an anonymity network. A malicious node may also correlate broadcasts, return manipulated data, or try to influence output selection. Running a local node avoids that remote source of trust; a trusted remote node over Tor or I2P is a lighter alternative.

Sharing your wallet address publicly or reusing it

While Monero stealth addresses protect you on the blockchain level, sharing your main wallet address on forums or profiles creates an out-of-band link. If someone associates your public address with your identity, they know that address belongs to you — even though they can't see your transactions. Use subaddresses for every separate context.

Ignoring wallet software updates

Monero undergoes regular network upgrades that improve privacy features and fix vulnerabilities. Running outdated wallet software can result in transaction failures, reduced privacy, or exposure to known bugs. Keep your wallet software updated through official channels and verify the update signatures before installing.

Treating subaddresses as separate identities

Subaddresses reduce public address reuse, but a payer knows the address it paid and outside records may connect contexts. Use separate wallets where genuine separation matters rather than assuming unlimited subaddresses provide unlimited identities.

Monero vs Bitcoin — Privacy Feature Comparison

Feature	Bitcoin (BTC)	Monero (XMR)
Transaction transparency	All transactions public by default	All transactions private by default
Sender privacy	Sender address visible on blockchain	Obscured by a 16-member ring containing 15 decoys
Receiver privacy	Receiver address visible on blockchain	Hidden via one-time stealth addresses
Amount visibility	Amounts visible on blockchain	Hidden via RingCT Pedersen commitments
Chain analysis resistance	Lower — public transaction graph supports chain analysis	Higher — transaction graph is obscured, but off-chain evidence can remain
Fungibility	Public history can lead services to treat outputs differently	Designed for stronger fungibility by hiding transaction history
Block time	~10 minutes	~2 minutes
Mining algorithm	SHA-256 (ASIC-dominated)	RandomX (CPU-optimized, ASIC-resistant)

The practical difference is what the public ledger reveals. Bitcoin exposes addresses, amounts, and transaction links. Monero conceals those fields by default, trading easy public auditability for stronger transactional privacy. The Monero technical specification describes each protection and, importantly, labels sender privacy as probabilistic rather than absolute.