Bitcoin.conf settings

[ghost]

I am unable to locate an updated explanation of bitcoin.conf. An old, outdated guide is found at the wiki at https://en.bitcoin.it/wiki/Running_Bitcoin#Bitcoin.conf_Configuration_File. There is a developer's guide at https://bitcoin.org/en/developer-reference#bitcoin-core-apis but it is unclear if these commands are a complete list of what can be put into bitcoin.conf.

The settings are for end users rather than developers and would be placed at https://bitcoin.org/en/how-it-works. I am unable to find an updated reference for bitcoin.conf settings and I can't find the page https://bitcoin.org/en/how-it-works in the Github repository.

[gmaxwell]

but it is unclear if these commands are a complete list of what can be put into bitcoin.conf

The complete list is given by running bitcoind -help

Most of the commands shouldn't be used unless you need them. The best example.conf is basically empty. We've had some tech support overhead in the past with people copying the old one from the wiki and ending up with a bunch of crazy settings.

[ghost]

Running the -help command means you need to run a command line and many users won't do that because it requires an extra step. The .conf file can be used to do things such as set up a proxy or other user settings. Some of the changes made in the developers in Bitcoin core are default settings. Some people have complained about the default settings for one reason or another. Gavin has responded that he merely sets default settings that can be changed by the user. However, there is no up-to-date reference for users to change the settings.

By running -help I believe it lists all commands and not just the ones that would change settings in the .conf file so there is 2 levels of confusion, first using command line and second to figure out which commands relate to changing seeing rather than returning data.

[saivann]

As far as I'm concerned, I think whoever is technical enough to play with configuration files should know how to run bitcoind --help. "man " and " --help" are so common that they're almost a standard. I'm not sure that maintaining an up to date copy on bitcoin.org is worth the effort (especially given that bitcoin.org isn't only about Bitcoin Core).

[ghost]

@saivann - Your concern as an experienced user is not the issue. I am in touch with new users and you only interact with experienced users and you don't consider their position. Users who are inexperienced in command lines and such will never use any command line at all. In particular, they may wish to connect to a specific node to prevent their Ip address from being captured or to connect to a node because it has high bandwidth. This only involves updating bitcoin.conf and does not involve command line. The only reference is outdated so obviously it was deemed important enough to publish previously. There is no basis for removing it, or more specifically, keeping an incorrect version.

Bitcoin.org is the site for the Bitcoin core project. it also solicits donations for the Bitcoin Foundation and provides other information. That is not a reason not to publish basic information about Bitcoin Core to supplement the info that is already there.

It does not appear reasonable to argue against providing documentation of the commands used in the .conf file. You have already stated in another thread that you would reject my issues because you don't agree with my attitude so your complaints have nothing to do with the actual issue. You just search for excuses to deny anything I say so you can close the issue.

[luke-jr]

@millybitcoin I suggest updating the wiki page. That's as good a place as any, and requires less effort to maintain.

[ghost]

The documentation should all be in one place and most of the information is already in the development guide at Bitcoin.org so your idea would break it into two places.

You don't deal with regular users and you are out of touch with their needs. It is complicated enough without having conflicting information in 2 places. One user points here and another points to the wiki and it creates confusion. People running the show here don't like people who don't have a deep understanding of Bitcoin and they get annoyed with people who don't/can't use command lines, github, etc.

[luke-jr]

@millybitcoin Weren't you just saying this is for end users, not developers? We shouldn't have stuff for end-users in the development guide, I agree with you on that...

[saivann]

I too would prefer we people update the existing wiki page instead of duplicating everything and ending up with just more conflicting and outdated pages. In general, work on bitcoin.org was focused on doing things the wiki couldn't do, because there's little value in duplicating work.

Of course and as always, unless perhaps if someone wanted to take the responsibility of doing the work and keeping it updated every time a new version is released.

[ghost]

The information overlaps between developers and users. You two are just searching for reasons to reject it so it doesn't matter what I say. As you know I already suggested that as information is being placed here it should be removed from the wiki with a link here to end the current situation that we have now which is sometimes duplicated and sometimes outdated information. I see confusion over this all the time.

The previous item was closed and locked and the excuse was nobody specifically agreed with what I requested when numerous other pull requests were approved under the exact same circumstances. Now you are arguing that we should keep essentially the same information in two places, I have tried to end that practice and you have twisted around to say that I am suggesting duplicating information. The other suggestion was within the past couple hours in another thread so you are now pretending that didn't take place. You really go to great lengths to drive people away.

I'll tip my hat to the new constitution, Take a bow for the new revolution ... Meet the new boss
... Same as the old boss.

[luke-jr]

Bitcoin.org really shouldn't have Bitcoin Core specific content anyway.

[ghost]

Of course bitcoin.org should have Bitcoin Core information. Satoshi set the site up that way and gave the site away to be used for that purpose. I think there should be nothing else. The other information should be left up to the free market rather than under a centralized control by those that are leveraging the SEO from the site. It has the SEO because it was set up as the Bitcoin Core collaboration web site and now the site has been essentially hijacked. That is consistent with other things that have happened when the Foundation is involved in something.

[saivann]

@millybitcoin You keep using personal attacks and wasting contributors time even though there are valid options suggested and basic requirements for implementing your idea are made clearer.

Accordingly, I am closing and locking this issue and will delete future comments and issues from MillyBitcoin. Whoever wants to not receive notifications from MilliBitcoin can click the "Block user" button near the "Follow" button here: https://github.com/MillyBitcoin .

Again, work is welcome if someone wants to update the wiki, or re-open the same discussion in case someone really think it's worth and is wiling to spend time creating, organizing and updating the page (and convince other contributors that it's a good idea).