So, from vers 0.13.0 in Aug, LND it has by default anchor output reserves activated. And is quite a nightmare for noobs that do not understand what is going on. This is like a ticking bomb about to explode. Many node runners still didn't notice it, but they will start soon seeing that cannot send funds or open channels. More discussions here: https://bitcoinops.org/en/topics/anchor-outputs/ https://github.com/lightningnetwork/lnd/issues/5599 https://github.com/lightningnetwork/lnd/issues/5648

I posted some requests / fixes to these apps, to see if more people come up with a nice solution: https://github.com/Ride-The-Lightning/RTL/issues/833 https://github.com/apotdevin/thunderhub/issues/352 https://github.com/getumbrel/umbrel/issues/1056

I tried editing the lnd.conf file with [protocol] protocol.no-anchors=true But still no luck to be able to open a channel from a single UTXO. Will try later (when mempool will be more empty) to send the funds to an external wallet and then send them back to the node new address to see if it works.

But this, already create many issues for noobs in those LN+ rings they try to open and all major wallet apps don't say too much about the error. Will create so much confusion. Those looking to open small channel will be crashed, with so many sats in "reserves", on top of commit_fees. Many will not understand this aspect.

What is your opinion on this, do you have a quick fix?