All three programs get settings from
dash.conf in the
DashCore application directory:
dash-cli, you will need to add a RPC password to your
dash.conf file. Both programs will read from the same file if both run on the same system as the same user, so any long random password will work:
You should also make the
dash.conf file only readable to its owner. On Linux, Mac OSX, and other Unix-like systems, this can be accomplished by running the following command in the Dash Core application directory:
chmod 0600 dash.conf
For development, it's safer and cheaper to use Dash's test network (testnettestnet - A global testing environment in which developers can obtain and spend duffs that have no real-world value on a network that is very similar to the Dash mainnet.), regression test moderegression test mode - A local testing environment in which developers can almost instantly generate blocks on demand for testing events, and can create private duffs with no real-world value. (regtest), or a developer network (devnetdevnet - A development environment in which developers can obtain and spend duffs that have no real-world value on a network that is very similar to the Dash mainnet. Multiple independent devnets can coexist without interference. Devnets can be either public or private.) described below.
In the following documentation, some strings have been shortened or wrapped: "[...]" indicates extra data was removed, and lines ending in a single backslash "\" are continued below. If you hover over a cross-reference link, a brief definition of the term will be displayed.
Updated about 2 years ago