Replies (11)

their taproot code is taken from decred's codebase, for one thing. it doesn't have full implementation of BIP-340, despite this, it fails on the last 4 tests in the suite, and i fixed it and pointed them to it in an issue but i got some dodge from roasbeef about why they didn't properly implement the tests. (for irregular length message signing). as a Go dev trying to work with bitcoin and lightning their BTCD and LND codebases are a shitstorm of stupid. the damn btcd has dependencies to prior versions of itself, just for starters. the configuration system on both btcd and lnd doesn't work. i've tried to put some PRs up to get a few things fixed but they never merge them. even tried to chase an actual issue they had filed, that issue is still there, the patch is still dangling, and would take about two hours to merge in.
> as a Go dev trying to work with bitcoin and lightning their BTCD and LND codebases are a shitstorm of stupid. as a fellow Go dev I probably spent a total of 8 hours trying to orient myself in the LND codebase and came to the same conclusion.
yes, i did all that because it's needed for nostr. the rest of btcd code can be avoided if nostr is your main target. Lightning is not so easy to avoid the insanity. check the version and date on that. they haven't fixed this, yes i filed an issue, about a year ago, and if you naively try to import lnwire, for, things ilke, you know, millisats units, hoooeeee. lol! have fun staying extremely frustrated at go mod tidy. LND/BTCD devs need to be shamed for their terrible custodianship of the main Go codebase.
i hope to some day in the future fork and fix these projects. for now just going to chip away at it whenever it is needed.
Their full focus is on TapAss - Taproot Assets. It’s a copy of the RGB project implementation with VC money behind it This is what you get when big VC money is behind one specific protocol implementation (LND) Objective is USDT on LND which could enable the biggest trading pair BTCUSDT volume to move off exchanges and down to a protocol level
↑