Thread by @roasbeef

if you're running an lnd routing node, here're some tips to keep your node afloat during the current mempool storm ⛓️🌊⚡️:

1. You can use the BumpFee (`lncli wallet bumpfee`) command to use CPFP to increase fee rate of a txn (close, open, sweep, etc): lightning.engineering/api-docs/api/l…

the first fee bump will use CPFP (you can watch the current sweeps using `lncli wallet listsweeps), subsequent calls will use RBF to increase the fee rate of the package

it doesn't do effective ancestor fee rate calculation rn tho, we have a SoB intern working on that 😎

2. Try to open anchor output channels whenever possible. Anchor channels have a special output that can be used to CPFP force closures. Without this channel type, you *cannot* increase the fee of a force close txn (all other outputs timelocked)

You can do this on the cli with `lncli openchannel [...] --channel_type=anchors`. On the gRPC API you set `commitment_type` to `ANCHORS`: lightning.engineering/api-docs/api/l…

A more aggressive move would be using the ChannelAcceptor API to ensure your node *only* accepts anchor channels

3. Update your routing policy to be more conservative (lightning.engineering/api-docs/api/l…)

Some values you may want to consider increasing:
* min_htlc_msat: the smallest HTLC you'll carry
* time_lock_delta: a long CLTV delta gives more time for things to confirm, can avoid force closes

* fee_rate+base_fee_msat: higher chain fees means higher node operation cost, increase fees can help to offset that somewhat

the latest version of Lightning Terminal has a slick new dashboard that breaks down your cost+revenue:

https://twitter.com/MichaelLevin/status/1653427435063369733?s=20

4. For those with anchor channels, increase --max-commit-fee-rate-anchors. By default, the fee rate for an anchor commitment txn is clamped, to something just enough to get into the mempool. The code tries to make sure not too much is allocated to fees, but this knob can modulate

5. Update your default block conf target for incoming co-op close requests (`--coop-close-target-confs=n`). The initiator pays fees and the latest versions of lnd do more to have both sides satisfice sooner. The BumpFee call can also be used to increase the fee rate of coop close

6. Update to v0.16.2! The latest version will continually rebroadcast transactions in the background (before was just explicitly on restart), which can help to resurface txns that may have dropped out of the mempool. New version can also act on HTLC chain events more quickly

7. Consider selling channel liquidity on Lightning Pool 🏊‍♀️. If you set your rates properly, then you can ensure that the premium you receive covers both the channel open and future close

Latest version of Terminal Web includes a new public order book:

https://twitter.com/lightning/status/1651267084926738433?s=20

more details on the latest Pool UI + design updates (now taproot by default, so lower fees due to musig2 usage):

https://twitter.com/MichaelLevin/status/1655651256059191337?s=20