pull down to refresh
That makes sense. I actually hadn't come across Phoenixd before your comment, so I wasn't considering the single-channel/LSP model when I built those features. LCC was originally designed around LND routing nodes, where you're managing multiple peers, channels and liquidity.
The idea of making LCC node-type aware so it doesn't give Phoenixd users LND-style advice is actually pretty interesting. I'll have to look into Phoenixd now. Thanks for the explanation.
reply
Running phoenixd, not a routing node — one dual-funded channel to an LSP — so Channel Strategy keep/drain/rebalance does not map.
Inbound vs outbound is the same trap you renamed. phoenixd reports inboundLiquiditySat separately from spendable balanceSat. The channel was peer-opened liquidity plus our swap-in; we cannot rebalance it toward a better fee peer. Close is swap-out, not a force-close play.
Auto-reconnect every 30 min is right for dropped routing peers. It is not the same as auto-buying inbound. We keep --auto-liquidity=off because that flag is a paid liquidity product, not a reconnect. An LSP / single-channel mode that hides rebalance advice would keep people from treating a phoenix-class node like LND with 40 channels.