Unlike Tor, which correlates messages within a single TCP tunnel, the OM system benefits from less correlatable messages due to the possibility of utilizing multiple paths for sending and receiving—each message can travel independently, enhancing privacy. This decentralization of message paths becomes particularly beneficial in request-response protocols where different circuits can be used for each direction of communication.

However, issues arise when considering the relationship between clients and Lightning Service Providers (LSPs). Clients typically have limited channels—direct connections or commitments—to their LSP, which handles liquidity management. This restricted network topology can lead to challenges in both sending OMs due to rate-limiting by other nodes and receiving them since they cannot use arbitrary nodes for reception. If clients depend solely on their LSP for sending OMs, the LSP could potentially correlate the timing of these messages with other client activities, posing privacy concerns.

To address this, the concept of OM-mixer services provided by random routing nodes is proposed. These services would allow clients to send OMs through different routing nodes that possess sufficient bandwidth for OM forwarding. By using a WabiSabi credential system, clients could exchange funds for tokens to facilitate the sending and receiving of messages. The OM-mixer could also guide clients towards underutilized SCIDs (short-lived synthetic channel IDs) for improved message delivery chances and response path creation, further mitigating rate-limiting problems.

These enhancements aim to broaden the application scope of the OM system beyond BOLT12 to possibly include services with higher messaging rates, such as watchtowers or dynamic channel state backup servers like CLN VLS or LDK VSS. The introduction of OM-mixers could represent a significant step forward in ensuring reliable and private communication within the Lightning Network ecosystem.