Onion Message Jamming in the Lightning Network

The discussion around the implementation of onion messages and HTLCs (Hashed Timelock Contracts) in blockchain protocols addresses several key issues concerning efficiency and spam prevention. The primary design goal for onion messages is to avoid frequent disk access, thereby enhancing performance. Attaching an unconditional fee to each onion message contradicts this objective because it could undermine the efficiency by necessitating frequent disk writes. This leads to a suggestion of using a batching approach as an alternative. However, such a method might not align well with the operational dynamics of HTLCs, where fees are integrated into the update_add_htlc transactions.

In terms of protocol mechanics, HTLCs and onion messages operate under different conditions despite their superficial similarities in handling fees. HTLCs encourage nodes to forward transactions with the anticipation of earning a fee upon successful payment completion. Conversely, onion messages present a risk wherein the counterparty might discard the message after receiving the fee, with no subsequent benefits or obligations. This difference underscores the need for distinct protocol mechanisms for each type of transaction to manage state and exchange processes effectively.

Moreover, there is an inherent challenge in setting appropriate policies for unconditional fees due to the absence of direct protocol support for onion messages, unlike HTLCs. This situation might necessitate shifting the burden of deciding these fees onto the users or adopting a standardized global fee policy. Additionally, the broader strategic approach to integrating such features should begin with evaluating their necessity and effectiveness within the protocol before exploring more complex solutions like staking, e-cash, or tokens that could complicate the system without clear advantages.