I just synced my wallet for the first time using just a Bitcoin Node. It took like 20 minutes.
It's kind of crazy that a Node doesn't have an indexer and I need to use something extra like Electrum
Login to reply
Replies (10)
That’s what completely LOST me about Bitcoin when I first started running the code
yeah, I agree, it's fucking crazy
It makes me want to get really proficient in C++ lol
It makes me want to build my own implementation in Go... Or more realistically contribute to btcd
Lol I thought exactly about this. But 3 people run btcd.
What worries me is that someone will do the effort of making an index and if it's not a GIGAbrain index that does everything in 10 nanoseconds it would not get merged
half the people who run lnd run btcd, it's the de facto default way to run LND.
if anyone wants to fork BTCD and make it really fucking awesome i'm putting my hand up to join the effort. i know the codebase extremely well and the numerous mistakes it has in it, and i have a bunch of new tools to speed up its cryptography, and i'm sure i can make it do IBD fast the same way as bitcoin core. it's surely a procedure that allows skipping a lot of hash grinding.
also, yeah, pruned nodes, idk if it has that yet, but likely if it does it's not a stable feature yet would be my guess based on my observations of progress of that project in the trajectory of the last 8 years.
I thought you had to link to btcd in lnd. that it wasn't run by default. Interesting...
the tooling nudges you towards this configuration and so it came to dominate.
couple years ago there was an issue related to the taproot push limit that broke half the lightning network. yes, the one that let the spam party begin, the flaw between the segwit witness section and the taproot witness push limit.
so, yeah, at least, it used to be the most common node backing LND. zap wallet also used neutrino, to connect to btcd for the SPV