this is one of the most salient reasons why it is a sad state of affairs that the Go implementation of bitcoin is so poorly funded and maintained:

building bitcoin core, in comparison, is 15-60 minutes depending on how much of the preparation work and how fast your internet connection is to download over half a gigabyte of material to be able to do it.

btcd repository is 45mb in size, go compiler is 120mb.

not only that, but half the lightning network runs off btcd via lnd.

yet everyone is swallowing this hooey that bitcoin core is the canonical version.

it's a close competitor to node_modules for its mass.

sure, you can nit pick and point out that btcd doesn't have a GUI on it but seriously, um. yeah. btcd + zap wallet gives you all that plus lightning.

(btw, i helped fix zap so it could be used with your own btcd, the configuration wasn't persisting when i tried it and they fixed it days later).

jack mallers and several other bitcoin devs will tell you that you can do way more with Go than you can with this other 50 different tools garbage.

Reply to this note

Please Login to reply.

Discussion

Yes

i'm just running it again (a slightly modified version built with my consolidated version of the elliptic curve and chainhash libraries the consolidated versions taken from btcsuite/btcd/btcec and decred/dcrd/dcrec - i did it to get rid of the decred link!) and very pleased to see that at last it seems that checkpoints are working properly.

it's powering through, already at 100k blocks in under 3 minutes...

weeeiilllll... ok, now it's back to slow mode after that. no idea why. i know it's validating every block when its clearance rate drops under 2000 blocks/s.

gonna add the AVX2 SHA256 implementation to my modifications now, see if it helps push the block validation rate a bit more.

This is the lib that took down like 70% of the lightning network right when someone yeeted a taproot tx onto the chain right?