Disclosure: Critical vulnerabilities fixed in LND 0.19.0

In the realm of the Lightning Network, a critical aspect for discussion pertains to the handling of the total balance within a channel through concurrent Hashed Time-Locked Contracts (HTLCs). A particular channel parameter, max_htlc_value_in_flight_msat, exists specifically to set limitations on this capability. However, it's noteworthy that LND, a popular implementation of the Lightning Network protocol, adopts a default stance that does not impose any limit on the max_htlc_value_in_flight_msat. This approach essentially allows for the entire balance of a channel to be utilized in concurrent HTLCs without any restrictions. Furthermore, upon review of LND's codebase, as indicated by the provided link, it becomes apparent that there is no available mechanism to modify this default behavior. This characteristic of LND underscores a significant operational nuance within the Lightning Network's ecosystem, highlighting the flexibility extended to channel balances but also introducing considerations regarding risk and liquidity management.