Nostr Web Client

also, nothing against lopp’s work but encouraging users to get their config from some 3rd party on the internet is a nightmare. you can reeeeaally fuck up someone’s node with the config settings , and most users using sites like lopps probably aren’t able to vet whether or not the explanations and generated configs are malicious or not.

i’ve been planning to slowly add more detailed examples to the help output of bitcoind, would love to collab if you have ideas/suggestions

waxwing 2y ago

Josie,

thanks for the detailed answer!

So it seems my question was just out of date.

Because I can see now that in the *latest* binary distribution, indeed a full commented bitcoin.conf is right there at the top level of the directory tree.

It wasn't there in v0.21 but it is there in v24+ so it must have changed in between.

So what we have now is exactly how I expected it to be.

I agree that auto-generation from a website isn't great.

Reply to this note

Please Login to reply.

Discussion

josie 2y ago

yep! the PR was merged in may 2022 iirc, so it should be available as early as v23.1.

you can also use the script to generate an accurate config for any previous release. so let’s say you want a full commented out config for 0.21 - all you’d need to do is download 0.21 (or compile it) and then set the BITCOIND env variable before running the script