Welcome to the next crypto level
← Nexorena

security

Monero considers a random delay for relaying transactions received over Tor and I2P

A November 13 change would accept these transactions only on inbound connections and relay them after a variable delay. The proposal remains under review.

Nexorena Editorial Team

Monero considers a random delay for relaying transactions received over Tor and I2P

A second proposal after the first round of feedback

A change to Monero’s software was proposed on November 13, 2026, to make transaction relay more uniform for transactions received over Tor and I2P. In the project repository, contributor selsta presented it as an alternative to a first proposal opened on November 8, following feedback from another developer. The new change is under review. Its submission does not mean it has been merged into the main codebase or released to operators.

The change concerns peer-to-peer connections. An inbound connection is opened by a peer toward the node receiving the transaction. An outbound connection starts in the opposite direction. The proposal would accept Tor and I2P transactions only on inbound connections. This rule applies when a node receives a transaction and decides how to relay it. It does not change how wallets sign transactions or how the network validates blocks.

Forwarding to the public network would wait a variable time

The proposed code would forward transactions received this way after a randomized delay. They would then enter the public Dandelion++ relay process, which propagates them in stages. Under the change, the receiving node would apply the delay even if the sending peer asks for broad broadcast. That signal could no longer bypass the handling intended for transactions arriving over Tor or I2P.

The aim is to reduce the value of timing clues. When a message received on one connection is followed immediately by its broadcast on another, an observer can use the timing of the two events as a clue that they are linked. A variable delay weakens that direct association. Monero’s documentation says Dandelion++ makes transaction origins harder to trace on the public network, with limits against the first node that receives them or the user’s internet provider.

Handling transactions the node already knows about

The proposal also changes how a node tracks the state of a transaction in its pool. A node may already know about a transaction when another copy arrives through a different connection. The fix would preserve the delay if a relay operation already underway finishes afterward. The change includes tests for how the software updates a transaction’s state when it returns through the public network.

The proposal is labeled as needing a backport to a maintenance branch. That label sets neither a release version nor an availability date. Operators can follow a merge decision and the notes for any release that eventually carries it. The November 13 request describes a change to relay between peers that is still being reviewed by maintainers.

Article sources

Written with love byOlivia ParkerMeet this editorial pen name ↗

Explorer Nexorena