pull down to refresh

155 sats \ 2 replies \ @nikotsla 6 Apr \ on: Liquidity squeezing from your node lightning

Just to add more info, this strategy get my attention: https://github.com/zapomatic/zap_lnd_tools?tab=readme-ov-file#cooperative-fee-strategy by @zapomatic

With time you can identify this type of node and act accordingly:

  • Blacklist
  • Only open big channels so you can close the channel without losing sats once the liquidity is in the other side (capital intensive).
  • Set max_htlc so low that the drain take a lot of time an effort
write
preview
212 sats \ 0 replies \ @DarthCoin 6 Apr
Set max_htlc so low that the drain take a lot of time an effort

Yes, that "valve method" by Rene Pickhardt works pretty nice. Also is forcing users to use MPP.

reply
100 sats \ 0 replies \ @zapomatic 7 Apr

Static HTLC max is good. The dynamic HTLC setting has proven to be a bad idea with current tech--as balances in flight mess with liquidity observation--a solvable problem but not one that is currently solved.

Currently, it's better to leave HTLC max static. Using inbound fee discounts and setting fee buckets has proven to be a nice way to not need to manually rebalance and allow flow to be more natural.

reply