Overview: Dash Masternode
...on Fedora, CentOS or Red Hat Enterprise Linux
Manage a Dash Masternode like a systems administrator.
The objective of this set of documents is to illustrate how you can operate a Dash Masternode. This requires setting up a collateral-bearing wallet on one system and a full node configured to be a masternode on a another. Using this guidance, you can manage a robust Masternode deployment that once set up, requires little maintenance expect the occassional update or upgrade.
These instructions are specific to the Red Hat-family of linuxes.
The overview (this document):
Wallet setup: Set up a Dash Wallet in support of a Dash Masternode
Masternode setup: Configure and Run a Dash Masternode as SystemD Service
Discussion about security: Configure FirewallD and Fail2Ban on a Dash Masternode
Troubleshooting: Dash Core Troubleshooting Guide
Upgrading Major Versions: How to Upgrade from Version 12.2 to 12.3
Upgrading OS: How to Upgrade Your Masternode's Operating System
What is Dash and what is a Dash Masternode?
Dash (Digital Cash) is an open source peer-to-peer cryptocurrency that offers instant transactions (InstantSend), private transactions (PrivateSend) and token fungibility. Dash operates a decentralized governance and budgeting system, making it the first decentralized autonomous organization (DAO). Dash is also a platform for innovative decentralized crypto-tech.
A Dash Full Node is a un-collatoralized member of a decentralized network of servers that validate transactions and blocks.
A Dash Masternode is a member of a network of incentivized servers that perform expanded critical services for the Dash cryptocurrency protocol above and beyond the services of a full node.
Dash is open source and the name of the overarching project. Learn more at www.dash.org.
Wallets and Masternodes
Note that there are two systems involved here, one for the wallet and the other for the masternode.
To run a masternode, you set up a small server running a masternode as a service. But the owner of the masternode has to have 1000 DASH as collateral. Ownership of that collateral is provable by having a specially configured wallet, separate from the masternode that is used to start the masternode once configured. This of that wallet with that particular 1000 DASH as the ignitiion key for the masternode.
"I'm not tech savvy! Help!"
There are a number of services that will remove the headaches of managing a masternode yourself, host one for you, and walk you through the process of getting set up. Here is a listing of the current providers recommended by the Dash community.
I was really looking for a guide for a different platform. Help!"*
Check out the guidance found in the official dash core documentation: https://docs.dash.org/en/latest/masternodes/index.html
Setting up a Dash Masternode: The high-level process
- Save up 1000 DASH
- Install and populate a collateralized Wallet
- Install a Dash Full Node with dreams of being a Masternode
- Bind the wallet to the node and have it "start" the Masternode
- Install Sentinel on the same server as the Masternode
Sounds easy, right? Well, on the whole, it is not complicated, just "tricky". Maybe "twitchy" is the right term.
A note about Testnet versus Mainnet
There are two Dash networks. Two blockchains, separate sets of miners, wallets, nodes, and masternodes. Testnet exists to as a proving grounds for new code and new ideas. You too can use it to get familiar with Dash and how all these pieces fit together. It uses freely available testnet Dash (tDash) which can be acquired here. Mainnet is the network that secures, mines, and transacts real Dash of real value.
You can actually switch freely between Mainnet and Testnet. It's almost like a shadow network. Always there... just beyond our ability to see clearly... ;)
There are a number of places where you tell all the various Dash Core executables that you are operating on the testnet or not.
dash.conf - for
dash-qt, and tools like
testnet=0— Default is usually
testnet=0for stable releases.
Data directory: Usually either
testnet=1, your data-directory becomes your data-directory/testnet3
dash.confis independent of this, even if you choose to store it in your data-directory.
network=mainnet— Leave this commented out and allow
dash.confto determine Sentinel's operating posture.
These packages are built and tested. But just like with cryptocurrency, you must assume the risk associated to this space. I only claim that I made a best effort to build packages that work and function as expected. They may not in your context. Additionally, these packages are built from code provided by the Dash community. I have zero control over any vulnerabilities that code may contain. Please test your configation thoroughly before associating significant sums of money. Dash carefully!
Good luck! Comments and Feedback...
Got a dash of feedback? ...har har... Send it my way https://keybase.io/toddwarner
All documents in this directory tree are CC-BY-SA