Author: Matt Corallo 2023-02-16 00:42:54
Published on: 2023-02-16T00:42:54+00:00
In a thread discussing how to maintain outbound liquidity on the Lightning Network, Joost Jager asks how to set the flag for maintaining high availability (HA) without a credit relationship. He questions whether setting the flag based on channel saturation could result in errors and whether it is possible to avoid punishment from senders if HA guarantees are not met due to large flows. In response, the suggestion is made to open new channels, rebalance, or swap-in in time to maintain outbound liquidity. Jager questions whether publicly visible data can give accurate payment success rates for evaluating the network as a whole. There are three relevant categories of nodes: large nodes sending lots of payments, client nodes connecting to an LSP or two, and routing nodes that do not send many payments. For category (a), we may not need extra measures beyond improving scoring algorithms. Category (b) can be solved by downloading data from a node in category (a), while category (c) is trickier but can be addressed through fetching semi-trusted data. By doing so, everyone can have a similar experience as the River report.
Updated on: 2023-06-03T11:52:23.562865+00:00