Author: Vincenzo Palazzo 2023-05-11 07:15:12
Published on: 2023-05-11T07:15:12+00:00
The email update discusses the upcoming call for channel jamming, which is scheduled for 15:00 UTC on Monday, May 1. The agenda for the meeting can be found on GitHub. The email also mentions the gathering of data during these weekly calls to mitigate jamming. The goals include observing the effect of logging-only implementation in steady state and gathering real-world data for future simulation work. Different algorithms for tracking local reputation will also be experimented with.Minimal changes required to add HTLC endorsement are outlined in [2]. A binary endorsement field is suggested to start with, and as more is learned, a more expressive value may be required. There is interest in deploying using an experimental TLV value. The email proposes a two-part scheme for mitigating channel jamming: reputation for slow jams that are easily detected as misbehavior and unconditional fees for quick jams that are difficult to detect, as they can always fall under a target threshold.Each node tracks the reputation of its direct neighbors and allocates a number of slots reserved for endorsed HTLCs from high reputation peers, as well as a portion of liquidity reserved for endorsed HTLCs from high reputation peers. Forwarding of HTLCs depends on whether or not a HTLC is endorsed by a high reputation peer. If it is, it is forwarded as usual with endorsed = 1. Otherwise, it is forwarded with endorsed = 0 if there are slots and liquidity available for unknown HTLCs.Finally, the email ends with some offers to help with implementation details and an expression of gratitude for the helpful updates.
Updated on: 2023-06-03T12:51:18.075947+00:00