The purpose of this tutorial is to walk through the steps necessary to set up a masternode with Dash Platform services.
Running a masternode requires familiarity with Dash Platform services. Improper configuration may impact testing so please exercise caution if running a masternode.
- Access to a Linux VPS (Ubuntu 20.04 LTS recommended) configured with a non-root user (guide)
- Docker (v18.06.0+) and docker-compose (v1.25.0+) installed
- An installation of NodeJS v12+
- A copy of the mn-bootstrap repository
Clone the mn-bootstrap repository
git clone -b master https://github.com/dashevo/mn-bootstrap.git cd mn-bootstrap npm install # optional: install CLI dependencies sudo npm link # optional: link CLI for system-wide execution
Full Platform Node
A full node that with all Platform services can be started by simply running the setup command with the node type setup parameter set to
fullnodeand then starting the node.
mn setup testnet fullnode mn start
First, obtain 1000 Evonet tDASH and create your protx registration transaction as described here. The Dash Core Full Node tutorial has an example configuration file that can be used to connect to Testnet with Dash Core.
The Dash required for the masternode collateral may be obtained from the faucet (it may take several requests to get the full amount).
Select the testnet config, set the IP address, and the BLS key used in the previous step:
node bin/mn config:default testnet node bin/mn config:set externalIp <your IP> node bin/mn config:set core.masternode.operator.privateKey <your BLS private key>
node bin/mn start node bin/mn stop
More comprehensive details of using the mn-bootstrap tool can be found in the mn-bootstrap README.
Updated almost 3 years ago