Every Monero transaction hides three things at once: who sent it, who received it, and how much moved. Those are three separate mechanisms doing three separate jobs, and none of them require you to change a setting. Ring signatures mix the real spender into a crowd of decoys. Stealth addresses put a fresh one-time address on every transaction so your public address never appears on chain. RingCT locks the amounts away so an observer cannot read the value. Here is what each one actually does, what it does not protect against, and what that means for how you use the wallet.
Ring signatures: hiding the sender
When your wallet spends an output, it cannot just say “I am spending output number 4,091”. That would link the transaction straight back to you. Instead, the wallet assembles a ring: your real output plus a set of decoy outputs taken from the blockchain, outputs other people have already received. The current protocol sets the ring size at 16, so a transaction presents 16 equally possible sources and a signature that proves the right one signed without saying which one.
The decoys aren’t chosen by you. The wallet picks them automatically from the chain, following protocol rules about age and distribution, precisely so nobody can bias the selection. An observer watching the transaction sees 16 candidate inputs with no way to tell which was spent.
The crowd has grown over the years, from a handful of decoys in the early days to the current 16, because researchers kept finding ways to narrow smaller rings. The history is worth knowing for one reason: advice written before 2018 about manual mixin settings and ring sizes is obsolete, and following it today can only hurt you.
The honest limit: this is probability, not magic. If a decoy output is later spent in its own transaction, it was by definition a real spend, not a decoy, and careful analysis can narrow crowds over time. The protocol work on this never stops. For a user, the practical takeaway is simpler: never manually “improve” the selection, and do not reuse the same output across rushed rapid spends. Let the wallet do its job.
Stealth addresses: hiding the receiver
Your public Monero address, the one starting with 4 or 8, never appears on the blockchain. What appears on every transaction is a one-time destination key, derived by the sender from your public address plus random data that never gets published. Only the recipient can scan the chain, recognize the key as theirs and spend from it later.
This kills the address-reuse problem that leaks so much on transparent chains. Every transaction gets a unique destination, even when a hundred payments arrive at the same public address. There is no way to build an address blacklist of “known Monero users”, because there are no addresses on chain to blacklist.
The one-time keys are how a view key does its job. A view key lets someone else scan the chain and see which transactions were sent to you, without being able to spend anything. That is what makes it useful for proving a payment happened in a dispute, without handing over the wallet.
RingCT: hiding the amount
The third piece is the transaction amount. RingCT, live since 2017, replaces the plaintext number with a cryptographic commitment. The math proves two things without revealing the value: that the inputs and outputs balance to zero, and that no amount is negative, so nobody mints coins out of thin air. An observer sees a valid transaction and cannot read the sum.
You do not interact with RingCT. It is worth knowing only because it is why fee estimates and change handling behave the way they do: the wallet knows your amounts, the network does not.
What none of this hides
None of the three mechanisms touches the network layer. Whoever you connect to when broadcasting, a remote node operator or your internet provider, can see that your IP produced traffic at that moment. Timing and broadcast patterns are the classic weak point, and ring signatures do nothing about them. The same goes for onramps: an exchange that knows your identity knows you bought Monero, whatever the chain itself hides afterwards. If network-level privacy matters to you, that’s a node policy question, not a transaction question, and it’s the one genuine decision Monero asks of a user. Our comparison of remote nodes versus running your own node covers exactly that tradeoff.
The other limit to keep in mind: privacy is not the same as anonymity from a motivated, targeted adversary that controls other evidence. Monero’s privacy works by making mass surveillance expensive, not by promising invisibility. Claims of unbreakable anonymity oversell it, and so do we not.
Why beginners do not need to configure anything
Ring size, decoy selection and one-time keys are protocol defaults enforced by the network. There is no setting in any wallet to weaken or strengthen them, and there should not be. The two things that actually matter in your control are elsewhere: keep your seed words safe and offline, because seed loss is the one unrecoverable failure in this system, and pick your node policy deliberately, because it is the one privacy decision you actually make.
The short version
Ring signatures put your spend in a crowd of 16 so the sender stays ambiguous. Stealth addresses give every transaction a one-time receiver key so your address never appears on chain. RingCT blinds the amounts. Nothing in the wallet needs configuring. The real decisions you make are the seed backup and who you broadcast through, and those two matter more than any of the cryptography above.