خدمات الاستضافة#
يقدم العديد من أعضاء مجتمع داش خدمات استضافة ماسترنود. يمكن تحقيق هذه الخدمة بشكل آمن دون أن يتخلى العميل عن السيطرة على 1000 داش المطلوب للضمانات. لأسباب أمنية ، يوصى بشدة بالاحتفاظ بالضمانات على محفظة الأجهزة عند الاستفادة من خدمة الاستضافة. تتوفر قائمة بخدمات استضافة ماسترنود المتاحة حاليًا أدناه.
قائمة خدمات الاستضافة#
إخلاء المسؤولية: قد تكون شركة داش كور تابعة لأعضاء هذه المجتمع ، ولكنها لا تشارك في توفير أي من هذه الخدمات.
CrowdNode#
Allnodes#
SID Hosting Service#
Pool of Stake#
Staked#
NodeHub.io#
Gentarium#
Masternodehosting#
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:
أرسل 1000 داش إلى عنوان تتحكم فيه في معاملة واحدة وانتظر 15 تأكيدًا
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.