It always seems when I hear problems about an LN node impl, it’s always LND. 🤷♂️
Discussion
i know that codebase, and the associated btcd codebase very intimately.
it is like being in the room where the shit is hitting the fan trying to do anything with it. i mean literally, it will raise your blood pressure.
i wish i could clean it up because whoever is paying for its maintenance clearly is being ripped off, or not paying enough.
also, taproot is basically just a mechanism for addressing contract addresses. you have the root, which is a regular segwit address, and then you can tap into that with basically infinite sub-addresses.
some of the terminology and design and explanations of the things really leave something to be desired.
Sounds like a high time preference engineering nightmare. But it works so 🤷♂️
just the configuration system will have you tearing your hair out. one of the first things i did when I built https://github.com/p9c/p9 out of it was rip out the entire config and cli args parsing system.
it doesn't work. at all. changing things in configuration file, doesn't work. i just made a little patch the other day to use go 1.16 embed library to put the default configuration file in there so it writes it, and lo and behold, it writes it every time, and i spent 3 hours still not being able to figure out which code was calling the rewrite. i gave up on it.
i have several pending PRs on both btcd and lnd that i juts gave up on in disgust because i kept on having to merge back new changes into it and they still never did anything.
the behaviour of the project devs is really weird, idk wtf is going on out there, but it seems off.
i've basically moved towards taking pieces of it apart that will never get changed, probably, and i use them in my own code because the btcsuite/lightningnetwork codebases vomit on you if you touch anything.
This is a really interesting insight, thank you