why i waited to switch to #Knots
(Spoiler: i run it now. fork off, if you don't like it. but config matters.)
TL;DR
start9 shipped a broken default Knots config. it sent crazy-high fee estimates to LND. not knots' fault — it’s *powerful*, but that means you need to understand your config. check it.
context:
my node was once on the other side of this
peer force-closed a channel and paid an insane amount in fees. i thought, “hell no, don't touch knots with lnd”
but i kept watching. turns out the root cause was a stray comma in start9s default config.
not knots problem. just bad packaging.
**knots is good.**
more knobs, more visibility, more control than core.
Over 85% you dominate the network
Only 15% to disrupt it
control your node. but don’t blindly trust defaults - know what you’re running
final thought:
if you don’t understand your config, fix that. or it’ll cost you.
and to the peer who lost all those sats - hope you’re okay.
#bitcoin #lightning #bitcoinKnots
GitHub
[bug]: min_relay fee estimation issue when running with Bitcoin Knots · Issue #9048 · lightningnetwork/lnd
It's not my node. But it looks like the guy used Ind. There are force closures with other Lnd nodes (e.g. Garlic, Tatooine) that cost a couple mill...