Monero’s cryptography hides transaction details such as the recipient and amount, but blockchain privacy and network anonymity are different things. An observer may still try to link a transaction to the IP address of the device that first relayed it.
Monero uses Dandelion++ to make that analysis harder. But Dandelion++ does not hide a user’s IP address from every participant involved in sending a transaction. Its effectiveness depends on how the wallet connects to the network, which nodes relay the transaction, and how monerod is configured.
Why ordinary transaction propagation can expose a sender
Many P2P networks spread new transactions through flooding, or gossip: a node that receives an unfamiliar transaction announces it to its peers. This is fast, but it can give observers clues about where a transaction first appeared.
A neighboring node can record when it received a transaction and which peer sent it. That alone does not prove the peer created it; it may simply be forwarding someone else’s transaction. But an observer controlling many nodes can compare arrival times and estimate the likely source.
For Monero, this creates a network-level privacy risk even when transaction details remain cryptographically protected. An observer might not learn the payment amount or recipient, yet still associate a particular transaction with an IP address and time.
How Dandelion++ works
Dandelion++ spreads transactions in two stages: stem and fluff.
During the stem phase, a transaction travels along a narrow path through a small number of nodes. Eventually, one node switches it to the fluff phase, when it is broadcast more widely. To observers who see only that broad spread, the node that began fluffing the transaction may appear to be its source.
Monero’s implementation uses additional mechanisms, including changing routes and probabilistic transitions. These are intended to make propagation analysis harder, not to conceal a transaction from the node that directly receives it. That limitation is central to the first-hop problem.
The first hop matters
The first hop is the first network node that receives a transaction after it is created. If a wallet submits a transaction to a public remote node, that server is the first hop. Its operator can see the connecting IP address, the time of the request, and the transaction itself before relaying it with Dandelion++.
Dandelion++ may make the source harder to identify for other participants, but it cannot erase what the remote-node operator has already observed. A server that keeps connection logs can potentially associate a client’s IP address with transactions submitted through it. This does not give the operator the user’s private keys or necessarily reveal the payment’s amount or recipient, but it can compromise network-level anonymity.
Why running your own node is not a complete guarantee
Running your own monerod removes the need to submit transactions to an untrusted RPC server. However, a node using ordinary IPv4 or IPv6 connections may expose its public IP address to its P2P peers.
A node that accepts no incoming connections may also have fewer opportunities to receive and relay other people’s stem transactions. If it sends a new transaction to a stem peer, that peer may have less reason to regard it as an ordinary relay rather than the transaction’s origin. This does not prove that every outgoing transaction came from the node operator, but network reachability and node configuration can affect the inferences available to an observer.
Dandelion++ should therefore be understood as reducing the likelihood of source identification, not guaranteeing that no one can observe or infer the source.
Spy nodes and Sybil attacks
An adversary can operate multiple nodes to observe transaction propagation, collect IP addresses, and analyze network relationships. This is a form of Sybil attack: one operator uses many network identities.
If a transaction reaches an adversary-controlled node early in its stem route, that node can see which peer sent it. The peer may still be a relay, not the sender, so observers may also consider timing, connection direction, network reachability, and how many nodes they control.
Monero’s selection of stem peers from a node’s outbound connections provides some protection against an attacker who merely creates many inbound connections. Still, controlling enough reachable nodes may increase the chance of observing a transaction’s route. Users cannot always know who operates their peers, so Dandelion++ reduces risk rather than eliminating it.
Tor, I2P, --proxy, and --tx-proxy
Dandelion++ and Tor or I2P address different parts of the problem. Dandelion++ changes how a transaction propagates through P2P nodes; Tor and I2P help obscure the user’s network address.
In monerod, --proxy routes ordinary outgoing connections through a SOCKS proxy. By itself, it does not turn ordinary P2P connections into onion or I2P connections. The --tx-proxy option is intended to route locally created transactions through Tor or I2P.
This distinction can matter when a node synchronizes over clearnet but sends its own transactions through an anonymity network. P2P peers may still see the node’s IP during ordinary synchronization, while the transaction follows a separate route. Correct configuration and available Tor or I2P peers matter, and these networks have their own limitations.
Another option, --anonymous-inbound, allows a node configured with a hidden service to accept incoming P2P connections through Tor or I2P. If it receives and relays other people’s transactions, an outgoing transaction from that node may be harder to attribute to its operator: it could have arrived through an anonymous inbound connection. This offers plausible deniability, not absolute anonymity, and its value depends on the traffic and connections the node actually handles.
Remote nodes and wallet settings
Using a remote node through Tor or I2P can make it harder for the operator to identify a client’s real IP address from the connection. The operator can still see transactions submitted to the server. This differs from running your own node and routing its locally created transactions through --tx-proxy; the two approaches protect different parts of the connection.
Wallet behavior also matters. Some apps choose remote nodes automatically, switch between them, or use built-in network infrastructure. A wallet’s support for Monero and Dandelion++ does not by itself reveal how it sends transactions. For users with stronger privacy requirements, these details may matter more than extra interface features.
What this means for Monero privacy
It helps to distinguish three layers:
Transaction cryptography protects details such as the recipient, amount, and spent output.
P2P propagation is where Dandelion++ makes it harder to infer a transaction’s source from its route.
Network connections can expose IP addresses, connection times, and the fact that a particular client submitted a transaction.
A network-level leak does not automatically reveal a transaction’s amount, recipient, or true input. Those are separate privacy concerns and require different protections.
Dandelion++ makes transaction-source analysis harder, but it cannot automatically hide a client’s IP address from a remote node or fully protect a node using ordinary connections. Monero can conceal financial details effectively, while the sender’s network anonymity still depends on the first hop, monerod configuration, traffic routing, wallet behavior, and trust in the infrastructure through which the transaction first reaches the network.
Написать Join — чтобы участвовать в обсуждении.
this was major discussion amoungst the team for quite some time a while back
Ответы · 1
Ответы · 1
true