RouteBoost: Adding 'r=' fields to BOLT 11 invoices to flag capacity



Summary:

In a discussion about protecting the available bandwidth in a channel, Olaoluwa Osuntokun suggests that randomly rejecting packets is the only way to protect against probing. If a "prober" learns that a node has accepted a packet, they know that at least that amount of bandwidth is available. To protect against this kind of probing, a false capacity floor must be implemented and varied periodically. Randomly failing attempts as the channel approaches zero capacity are also subject to probing. The max_htlc value in the channel update can mitigate this issue, but multiple HTLCs can still be sent to ascertain available bandwidth. Probing one's own channel is pointless, as the discussion centers around probing someone else's channel.


Updated on: 2023-05-25T13:59:23.363537+00:00