Servicios de alojamiento#
Varios miembros de la comunidad Dash ofrecen servicios de alojamiento de masternodes. Este servicio se puede realizar de forma segura sin que el cliente ceda nunca el control de los 1000 DASH requeridos para la garantía. Por razones de seguridad, se recomienda encarecidamente mantener la garantía en una billetera de hardware cuando se aprovecha de un servicio de alojamiento. Una lista de los servicios de alojamiento de masternodes actualmente disponibles se presenta a continuación.
Lista de los servicios de alojamiento#
Descargo de responsabilidad: Dash Core puede estar afiliado a estos miembros de la comunidad, pero no está involucrado en la prestación de ninguno de estos servicios.
CrowdNode#

Operado por: CrowdNode ApS
Servicios: Alojamiento, Acciones.
Cost: 15% of masternode payments
Allnodes#

SID Hosting Service#

Zaimirai#

Pool of Stake#
Staked#

NodeHub.io#

Gentarium#
Alojamiento de masternode#
Operado por: flare (miembro del equipo de Dash Core)
Servicios: Alojamiento
Cost: €18/month
Registering a hosted masternode#
A list of available documentation appears below:
Information for users of hosted masternodes (you are here)
Registering a hosted masternode is done in several steps:
Envía 1000 DASH a una dirección que controles en una sola transacción y espera 15 confirmaciones
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.
Operator transactions#
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 dash.conf
file as descibed here to the masternode owner,
it will appear in the valid masternode 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 ipAndPort
,
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
masternode.
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.