0x363d0f0d363d…363d0f0a

ConfirmedSecurity526 vB143 sat/vB3 min decode

Monero Pull Request Aims to Close Tor and I2P Timing Leak

Monero PR #11743, filed November 13, proposes random delays and tighter relay rules for Tor and I2P transactions to block timing-based de-anonymization on the public network.

New Monero Privacy Update Might Be Coming Soon: Key Improvement
WitnessNew Monero Privacy Update Might Be Coming Soon: Key Improvementmadartzgraphics / pixabay

Outputs

  1. Monero pull request #11743 was opened on November 13 and remains pending review.

  2. The patch restricts Tor and I2P transactions to incoming connections and adds a randomized delay before Dandelion++ relay.

  3. The proposal is a reworked alternative to an earlier November 8 pull request by developer vtnerd.

  4. The PR carries a backport label, indicating it may reach the current release branch.

A Monero contributor has opened pull request #11743 on the project's GitHub, proposing changes to how nodes relay transactions arriving from Tor and I2P, according to the repository's public record. The patch, filed November 13 and still pending review, targets a timing side-channel that could let an observer link a transaction to the anonymity network it originated from.

The weakness sits in a specific relay mechanism. A node receives a transaction over Tor or I2P, then forwards it to the regular Monero network. The transaction stays private on its way in. Once it reaches public peers, that protection ends.

The problem is timing. If a transaction shows up on the public network immediately after arriving from Tor, an observer watching both sides can connect the two events and infer where the transaction came from. For users relying on Tor or I2P to hide their location, that inference defeats the purpose of routing through an anonymity network at all.

What would actually change?

The patch rewrites the rules for inbound privacy-network traffic in three concrete ways:

  • Nodes would only accept Tor and I2P transactions on incoming connections. Transactions arriving on outgoing anonymity connections would be ignored outright.
  • Accepted transactions would sit through a random delay before going anywhere. Only after that delay would they pass through Dandelion++, Monero's existing relay protocol that obscures a transaction's origin point as it propagates.
  • Senders would lose one option. Currently, a sender can request an immediate broadcast. Under the new rules, nodes would ignore that request on Tor and I2P connections, so no one can skip the delay.

The logic is straightforward: correlation attacks need predictable timing to work, and a randomized delay breaks that predictability before the transaction ever touches a public peer.

Where did the proposal come from?

The idea isn't new to the codebase. An earlier pull request, opened November 8 by Monero developer vtnerd, proposed a similar randomized delay for transactions moving from Tor and I2P to the public network. PR #11743 is an alternative to that earlier proposal, reworked after feedback from another Monero developer, according to the GitHub thread.

In code terms, the change is small. In operational terms, it closes a gap that matters to a specific class of users: those who route their Monero activity through Tor or I2P specifically to keep network-level observers from tying their transactions to an IP address or physical location.

What happens next?

Two things remain unresolved. First, the pull request is still pending review, so neither the revised relay behavior nor the removal of the immediate-broadcast flag is final. Second, there's no confirmed release date for when the patch would ship.

One signal does stand out: the PR is labeled for a backport. That label suggests the change could land not only in a future release but also in the current release branch, which would shorten the timeline for the fix reaching node operators in production.

Until review concludes and maintainers merge the code, the timing leak remains live on the network, and Tor and I2P users carry the correlation risk the patch is designed to eliminate.

via cryptonews.net (Source)

More from Daniel Okafor

Daniel Okafor

Show full bio

Correspondent covering people, launches and day-to-day practice in crypto and web3 industry at Mempool Brief.

1,221 articles