0x5d9699de5d96…5d9699db

ConfirmedSecurity537 vB110 sat/vB3 min decode

Monero Proposal Would Randomize Delays on Tor and I2P Transaction Relays

Monero pull request #11743 would add a randomized delay before nodes relay Tor and I2P transactions to public peers via Dandelion++. Review is open, no release date.

Monero Pull Request Would Delay Tor and I2P Transaction Relays
WitnessMonero Pull Request Would Delay Tor and I2P Transaction Relaysblickpixel / pixabay

Outputs

  1. Contributor selsta opened Monero pull request #11743 on Nov. 13; it was pending review as of Nov. 15.

  2. The proposal adds a randomized wait before nodes relay Tor and I2P transactions to public peers via Dandelion++.

  3. The delay applies even when the sender requests fluff relay or submits the transaction locally.

  4. The PR gives no release date, delay duration or estimate of risk reduction.

  5. It changes relay timing only, not Monero's ledger-level privacy mechanisms.

A Monero contributor has proposed forcing nodes to hold transactions from Tor and I2P for a randomized interval before relaying them to public peers. Contributor selsta opened pull request #11743 on Nov. 13, describing it as an "Alternative to #11711 after feedback from @vtnerd." The pull request remained open and pending review as of Nov. 15, with no release date or specified delay duration.

What would the pull request change?

The proposal changes how transfers move between anonymity networks and the wider internet. Under the proposed rules, nodes would send Tor and I2P transactions only over outbound connections and accept them only over inbound connections. Nodes would ignore transactions received over outbound connections to those networks.

After accepting a transaction, a node would wait a randomized interval before relaying it to public peers through Dandelion++, Monero's propagation-obfuscation protocol. The wait would apply even when the sender requests a "fluff" relay or first submits the transaction locally.

The change also touches the disable_noise option, which speeds broadcasts by letting a transaction go to an outbound Onion or I2P peer. The receiving hidden-service node can currently relay that transaction immediately to IPv4 or IPv6 peers. Under the proposal, the randomized wait would come first, before that node passes an accepted transaction on to public peers.

What risk does the delay address?

The target is a timing correlation attack. An observer monitoring both an anonymity network and the public network could compare when a transaction appears on each path and use the gap to link the two. The randomized wait would break that fixed timing relationship.

But the protection is partial. The proposal does not specify how long the wait should run, and it doesn't establish how much the delay would actually reduce the correlation risk. Those questions sit with reviewers.

Does this change Monero's core privacy?

No. The pull request concerns node-to-node relay timing only and describes no changes to Monero's ledger-level privacy mechanisms. Dandelion++ makes transaction propagation over public networks harder to trace, but it doesn't shield users from an internet service provider, a VPN provider or the first remote node that receives a transaction.

That distinction matters for operators. Anyone running a Monero node that bridges Tor, I2P and the clearnet would see changed relay behavior: longer holds on inbound anonymity-network transactions before they reach IPv4 or IPv6 peers, and stricter rules on which connection types carry which traffic.

For users, the practical effect is subtler. Transactions submitted through Tor or I2P could take longer to reach the public network, depending on where reviewers land on the delay's length. Nothing in the proposal alters balances, signatures or ring signatures — the mechanics that give Monero its on-chain privacy.

What happens next?

The pull request remains under review. It names no target release, no delay bounds and no metrics for measuring whether the timing obfuscation works. Until maintainers settle those parameters and merge the code, Monero's current relay behavior — immediate forwarding from hidden-service nodes to public peers under disable_noise — stays in place. The review window on #11743 is open, and the design questions it raises will have to be answered before any mainnet activation.

via tokenpost.com (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