A Proposal for Adding Bandwidth Metered Payment to Onion Messages



Summary:

Laolu and Rusty engaged in an email conversation centered on the Lightning Network technology. They discussed various topics, such as AMP and keysend specifications, which pertained to payment splitting and control over pulling all funds. Additionally, Laolu and Rusty talked about using HTLCs for sending data and rate limiting events.Lightning Labs has proposed a way to expand the scope of the Lightning Network beyond being just a decentralized peer-to-peer payment system. This proposal involves onion messaging, which would allow for sending and receiving invoices directly over the existing Lightning Network. However, there are issues with unsolicited messages, lack of compensation for network bandwidth expended by forwarding nodes, and rate limiting policies not being concretely addressed.To address these issues, an explicit onion messaging session creation is introduced with an optional payment for nodes that forward the onion messages. Nodes can signal their willingness to be paid to forward onion messages and specify their pricing using two new TLVs added to the node_announcement message: sats_per_byte and sats_per_block. A new TLV is added to the existing HTLC onion blob that allows a sending node to tender paid onion message session creation. After session creation succeeds, nodes will forward onion messages that include the onion_session_id. Nodes do the necessary bookkeeping to tally how much bandwidth is left in the session and check that the session hasn't expired before forwarding.Laolu and Rusty also discussed the idea of charging for forwarding onion messages, which can be implemented on top of existing onion_messages. They made references to specific resources such as bLIP and BOLT tracker. Furthermore, they touched upon incentivizing nodes to reliably forward messages.


Updated on: 2023-05-23T17:11:54.775014+00:00