enhancement: separate config files from cache directories about dash HOT 4 OPEN

The -testnet flag already does the right thing by creating a separate testnet3 which can be removed at any time without an issue (I think).

Fwiw, it is not safe to remove the testnet3 (or regtest or devnet-*) directory at any time. This is because wallet files for each network type are stored within that network's directory.

from dash.

Also, -datadir is a misnomer, at least from a user perspective. Perhaps that should be -cachedir and -userdir.

Or there should otherwise be some clear distinction between data that is "NOT unique" and "unique to this instance" and "unique to this user".

In the case of running a Full Node, I assume the purpose is just for creating APIs to interact with transactions and balances, etc, so it's not a big deal - but dashcore as a package doesn't really distinguish between use cases of "User is doing stuff with money" vs "Service provider is providing services" vs "MNO is voting" - everything is everything is everything, which makes it even more important to provide clear distinction at the folder level.

from dash.

The current behavior is also dangerous because there's no way to future-proof against it.

I can personally change -datadir and -conf, but then later -walletdir comes along and then -settings comes along and so on and so forth.

It needs to be the responsibility of the developers to choose safe defaults, not the responsibility of the user to be constantly vigilant in setting command line options, checking the notes of each release, etc, etc, etc.

Users are dumb. I'm dumb. Computers should protect us from our dumbness, not lead us into traps. People are bad at following rules and guidelines and methodologies, but computers are great at it. Y'know?

from dash.

wallet files for each network type are stored within that network's directory

I found a bug there too: #5423

from dash.