Several Dash community members offer masternode hosting services. This service can be realized securely without the customer ever giving up control of the 1000 DASH required for collateral. For security reasons, it is highly recommended to keep the collateral on a hardware wallet when taking advantage of a hosting service. A list of currently available masternode hosting services is available below.
List of hosting services¶
Disclaimer: Dash Core may be affiliated with these community members, but is not involved in the provision of any of these services.
SID Hosting Service¶
Pool of Stake¶
Registering a hosted masternode¶
Dash 0.13.0 implements DIP003, which introduces several changes to how a Dash masternode is set up and operated. A list of available documentation appears below:
Information for users of hosted masternodes (you are here)
It is highly recommended to first read at least the list of changes before continuing in order to familiarize yourself with the new concepts in DIP003.
Registering a hosted masternode is done in several steps:
Send 1000 DASH to an address you control in a single transaction and wait for 15 confirmations
Correspond with your hosting provider to determine who will generate the operator BLS keys, whether their fee will be paid by an operator reward percentage or according to a separate contract, and whether the masternode will be set up before or after the registration transaction
Prepare, sign and broadcast the registration transaction using Dash Core or DMT
It is highly recommended to store the keys to your masternode collateral on a hardware wallet for added security against hackers. Since the hardware wallet is only used to sign a transaction, there is no need to ever connect this wallet to the internet. However, a Dash Core wallet with balance (for the transaction fee) is required to submit the registration transaction. The masternode registration process closely follows the setup guide, beginning from the registration step.
This documentation is intended for operators managing nodes on behalf of
owners. If you provide an IP address and port of a synchronized full
node with your
masternodeblsprivkey entered in the
file as descibed here to the masternode owner,
it will appear in the DIP003 valid set immediately after they submit the
protx register_submit command as described above. If the full node
is not running, or if the owner submits
0 for the
then the node will be registered in a PoSe-banned state. In this case,
the operator will need to issue a ProUpServTx transaction to update the service features and register the
The ProRegTx submitted by the owner also specifies the percentage reward for the operator. It does not specify the operator’s reward address, so a ProUpServTx is also required to claim this reward by specifying a Dash address. If the reward is not claimed, it will be paid to the owner in full.