Transaction propagation and privacy
- Author
- CRYPTO PORT Editorial
- Published
- Updated
- Reading time
- 5 min
In short
Transactions spread across the network, and observing that spread from many vantage points can reveal which node emitted one first. Hiding what ends up on the ledger means little if the origin leaks during propagation. Protocol-level work to protect this stage is ongoing.
Key points
- Observing propagation order can pinpoint the originating node
- Deploying many listening nodes is a known technique
- Delaying and rerouting the first hop is a standard countermeasure
- It is a different layer from on-chain confidentiality
Definition
The problem that, as a transaction is relayed from node to node, observation can reveal where it was first emitted. It is the network-layer side of blockchain privacy.
In a peer-to-peer network, each node that receives a transaction forwards it onward. Implemented naively, nodes nearer the origin receive it sooner, so placing listeners widely and recording arrival times narrows down where it came from. Research has repeatedly demonstrated that this works.
The widely deployed countermeasure treats the first few hops differently from ordinary flooding: relay along a single path for a while before broadcasting widely, and randomise forwarding delays. That flattens the arrival-time gradient an observer would use to trace back.
This lowers the probability rather than eliminating the problem. If an attacker controls many of your peers, or if the same device keeps emitting over the same route for a long time, statistical narrowing remains possible. On-chain confidentiality and network-layer protection have to be reasoned about separately.
Watch out for
- · Privacy features in a protocol do not cover the network layer
- · Always using the same few peers makes you easier to observe
- · Light wallets usually broadcast through a provider rather than themselves