BIP 156 Dandelion Routing: Closed Privacy Proposal

This guide explains BIP 156 Dandelion in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.

Diffusion weakness

Ordinary diffusion sends a transaction to peers with delays. A well-connected observer can compare first-seen times and network topology to estimate the source. Encryption hides content only from the transport observer; Bitcoin peers still see the transaction and timing.

Stem and fluff phases

In the stem phase, one peer forwards along a selected path rather than broadcasting broadly. A later node switches to fluff and diffuses normally. Privacy depends on path unpredictability, honest participation and adversary coverage, while propagation reliability depends on timely fallback.

Epoch and path selection

The proposal changed routing choices over epochs so persistent patterns did not reveal a stable source relationship. Implementation needs secure randomness and consistent epoch handling without synchronised fingerprints. Reuse, biased selection or logging can undermine the theoretical model.

Embargo recovery

If stem forwarding stalls, an embargo timer eventually triggers diffusion so a malicious or failed next hop cannot suppress the transaction forever. Timing must balance privacy against reliability. Attackers may exploit predictable timeout behaviour to infer the stem source.

Graph and intersection attacks

Adversaries can operate many peers, observe repeated wallet broadcasts or manipulate connections. Dandelion improves one threat model but does not prevent all graph, timing or transaction-structure correlation. Coin selection, address reuse and clearnet administration remain separate privacy surfaces.

Closed status

Bitcoin Core does not promise BIP 156 stem routing. Research descendants such as Dandelion++ changed design details, but name similarity does not establish deployment. Never tell customers their origin IP is hidden solely because a wallet references Dandelion.

Simulation and measurement

Use a controlled network with honest and adversarial nodes, vary graph degree, adversary fraction, epoch, embargo and failures, then measure recall and propagation. Logs needed for research can themselves reveal origins, so sanitise and expire them under a privacy protocol. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness.

Conclusion

BIP 156 was a closed stem-and-fluff routing design that sharpened Bitcoin transaction-origin threat modelling. It is not a deployed anonymity guarantee, and practical privacy still spans wallet, peer and network layers.