...
The following guide is written with instructions to be executed as root. This is discouraged, but simplicity is the goal in mind - not security. You should modify these procedures to safeguard your assets as needed. You will be a target for hackers, and your Dash will be at risk. You are strongly encouraged to implement any and all restrictions available to you to protect your server from unauthorized access. These enhancements however, are beyond the scope of this guide.
Before you begin:
The following example is based on the following presumptions:
...
10 GB additional free disk space
2 GB of memory (RAM)
sudo (root) access to your CLI-based server
Download and install the components:
Start at the terminal prompt.
Determine which file to download from Dash:
At the CLI, you can easily determine if your server will support 64-bit. If you are unsure, then on your CAS terminal, type:
...
It should report something like: “CPU op-mode(s): 32-bit, 64-bit”
Use the modern 64-bit whenever possible.
If the command above comes back empty, you must use the 32-bit version.
Get the Dash wallet file download location:
Choose one method to use:
From your GUI browser:
Navigate to: https://www.dash.org/wallets/
Scroll down to “DESKTOP”.
Choose Linux.
Locate the link to the latest software for either 32 or 64 bit. The 32/64 decision is determined in the previous step. They are both the same interface, but modern systems are moving away from 32-bit.
Right-click on “Download TGZ” on Dash Core Linux 64 Bit (or 32 Bit).
Select Copy link address (or link location).
From the CLI terminal, enter (for 64-bit):
...
| Code Block |
|---|
DASHFile=${DASHURL##*/}
DASHVer=$( echo $DASHFile | cut -f2 -d"-" )
DASHDir=${DASHVer%.*} |
Download the Dash installation file:
Change to your home directory:
| Code Block |
|---|
cd ~ |
Next, you’ll use the URL already identified above to download the installation package:
| Code Block |
|---|
wget $DASHURL |
Extract Dash and set the appropriate permissions:
Create and enter a working directory for Dash:
...
| Code Block |
|---|
rm $DASHFile rm -r dashcore-$DASHDir/ cd ~/.dashcore |
Create an RPC token for CAS to communicate with dashd:
First, ensure that python is installed on your server:
| Code Block |
|---|
apt-get update apt-get install python-minimal |
Now create a Remote Procedure Call (RPC) token.
RPC is a method of communication between two programs. In this case, the two programs are CAS and dashd. The RPC token is designed to eliminate the need for hard-coded passwords in the involved configuration and script files. You will receive a password here ONCE. This password is required for CAS; it's your “RPC Password”. You must save it, preferably in a secure note file or database.
...
Save the name you entered above, the resulting token, AND the generated password. You'll need it in the next step. The “AnyNameYouWantHere” is the “RPC User”, and the password generated by the script is your “RPC Password”.
Create a dashd configuration file:
While you might (under certain circumstances) might want to start the daemon exclusively from a command line, we urge you to change the following settings within dash.conf and run dashd without parameters. Keep it simple!
...
Replace the “rpcauth=” info with the exact token generated in the previous step.
The line "rpcauth=" is one, unbroken line!
Start the dashd daemon (background process):
Once you have modified and saved dash.conf, start the daemon:
...
You may also need to configure your firewall to allow inbound connections to port 9999.
Add Dash to autostart when your CAS server boots up:
You will eventually want dashd to start automatically when the server boots. You should ensure everything works before you do this, though.
...
Save (using the defaults) and exit (using “nano”: ctrl-x).
Configure CAS to use Dash
Assemble the required information for CAS:
User: this is the “RPC User” you created earlier. For this example we'll just say it's “rpcuser”.
...
On a newly installed server, the list is normally empty and may be safely ignored.
Next, add a new crypto-currency type to CAS:
Enter the “Crypto Settings” menu in the left-hand column.
Click on the “+ ADD” button.
Create a suitable description, i.e. “Dash Local”.
Select “DASH” for the required “Crypto Currency*” setting.
Set Configuration Cash Currency* to “USD” (or whatever your local currency might be).
Set “Buy Rate Source” to whatever source you prefer.
Set “Minimum Cash Amount Per Transaction*” to zero – this enables any sale.
Select your Hot Wallet Buy source to “dashd”.
Enter the “Parameters” for the Hot Wallet Buy source as determined in the previous step. Example: “http:rpcuser:rpcpw:127.0.0.1:9998”
Click on “SUBMIT” to save your settings.
Finally, test it out:
Select “Test Hot Wallet Buy” from the RUN BTC SETTINGS TEST.
Presuming everything was entered correctly, you should receive confirmation of success!
You should also now configure the “Hot Wallet Sell” if you implement it.
That's it. All done!
...
UNINSTALLING DASH CORE:
Uninstallation is essentially the reverse order of installation. The following procedures will also delete any unposted transactions and is completely irreversible. Any Dash in your local wallet will be lost forever.
| Note |
|---|
|
Change your Crypto settings in CAS to reflect your replacement hot wallet.
In CAS, navigate to “Crypto Settings” and update all settings that involve Dash.
Login to your server CLI.
Shut down the dashd daemon:
Code Block dash-cli stop
(optional) Remove any startup references in crontab:
Code Block crontab -e
Finally, restore your firewall to block inbound connections to port 9999.
| Tip |
|---|
That's it - Dash has been stopped on your server, however the data files are left behind.
|
...
This may take a few minutes.
...
TROUBLESHOOTING DASH CORE:
You may discover that running a full node taxes your system dramatically. The following suggestions are offered to assist you in this regard. These pitfalls have nothing to do with CAS, and are offered merely as a courtesy to our valued customers.
...
Run dashd from a script
Implement dash.conf
Excessive server CPU load:
Shut down any web server. Any unnecessary programs should be eliminated.
...
Change your SSH port – attempts to hack into your server become greatly reduced.
Implement fail2ban – it will reduce the effects of attacks against your server.
FOR MORE INFORMATION:
Read the OFFICIAL documentation for installing & configuring DASH Core
...