التنصيب#

يتطلب إعداد ماسترنود فهمًا أساسيًا لتكنولوجيا لينكس و بلوكشين ، بالإضافة إلى القدرة على اتباع الإرشادات عن كثب. كما يتطلب صيانة دورية وأمنًا دقيقًا ، خاصةً إذا كنت لا تقوم بتخزين داش على محفظة الأجهزة. هناك بعض القرارات التي يجب اتخاذها على طول الطريق ، والخطوات الإضافية الاختيارية التي يجب اتخاذها لزيادة الأمان.

Commercial masternode hosting services are available if you prefer to delegate day-to-day operation of your masternode to a professional operator. When using these hosting services, you retain full control of the 1000 DASH collateral and pay an agreed percentage of your reward to the operator. It is also possible to delegate your voting keys to a representative, see the governance documentation for more information.

قبل البدأ#

This guide assumes you are setting up a single mainnet masternode for the first time. If you are updating a masternode, see here instead. You will need:

  • 1000 داش

  • محفظة لتخزين داش الخاص بك ، ويفضل أن تكون محفظة الأجهزة ، على الرغم من أن محفظة داش كور تدعم أيضا

  • خادم لينكس ، يفضل أن يكون خادمًا خاصًا افتراضيًا (VPS)

For information about hosted masternodes, see the documentation listed below:

This documentation describes the commands as if they were entered in the Dash Core GUI by opening the console from Window > Console, but the same result can be achieved on a masternode by entering the same commands and adding the prefix ~/.dashcore/dash-cli to each command.

Server configuration#

Proper server configuration is essential to successful masternode operation for both security and performance reasons. Refer to the Server configuration page for details on preparing your server to host a masternode.

أرسل الضمانات#

A Dash address with a single unspent transaction output (UTXO) of exactly 1000 DASH is required to operate a masternode. Once it has been sent, various keys regarding the transaction must be extracted for later entry in a configuration file and registration transaction as proof to write the configuration to the blockchain so the masternode can be included in the deterministic list.

A masternode can be registered from a hardware wallet, the official Dash Core wallet, or a Dash Electrum wallet, although a hardware wallet is highly recommended to enhance security and protect yourself against hacking. This guide will describe the steps for both hardware wallets and Dash Core.

ملاحظة

Details of registering a masternode with Dash Electrum can be found on the Electrum - Advanced Functions page.

الخيار 1: الإرسال من محفظة الأجهزة#

Set up your Trezor using the Trezor wallet at https://wallet.trezor.io/ and send a test transaction to verify that it is working properly. For help on this, see this guide - you may also choose to (carefully!) add a passphrase to your Trezor to further protect your collateral. Create a new account in your Trezor wallet by clicking Add account. Then click the Receive tab and send exactly 1000 DASH to the address displayed. If you are setting up multiple masternodes, send 1000 DASH to consecutive addresses within the same new account. You should see the transaction as soon as the first confirmation arrives, usually within a few minutes.

../../../_images/setup-collateral-trezor.png

تريزور محفظة تلقي علامة التبويب تظهر بنجاح تلقى ضمانات من 1000 داش#

بمجرد ظهور المعاملة ، انقر فوق رمز QR الموجود على اليسار لعرض المعاملة على بلوكشين. أبقِ هذه النافذة مفتوحة عندما نكمل الخطوات التالية ، حيث سنحتاج قريبًا إلى تأكيد وجود 15 تأكيدًا ، كما هو موضح في الصورة التالية.

../../../_images/setup-collateral-blocks.png

مستكشف Trezor بلوكشين يعرض 15 تأكيدًا لنقل الضمانات#

بينما ننتظر 15 تأكيدًا ، نزّل أحدث إصدار من أداة ماسترنود داش (DMT) من صفحة إصدارات GitHub هنا. بفك وتشغيل الملف. النافذة التالية تظهر.

../../../_images/setup-collateral-dmt-start.png

شاشة بدء تشغيل أداة ماسترنود داش#

Click the third button from the left Check Dash Network Connection in the top left corner of the main window to verify that the connection is working. Then connect your Trezor device and click the next button Test Hardware Wallet Connection to verify the Trezor connection is working.

../../../_images/setup-collateral-connection.png
../../../_images/setup-collateral-hardware.png

ماسترنود داش أداة تأكيد الاتصال ناجحة#

We will now use DMT to enter some basic information about the masternode and extract the transaction ID. Carry out the following sequence of steps as shown in this screenshot:

../../../_images/setup-collateral-dmt-steps.png

خطوات تهيئة أداة ماسترنود داش#

  1. Click the New button.

  2. Enter a name for your masternode. The host name you specified for your VPS above is a good choice.

  3. Enter the IP address of your masternode. This was given to you by the VPS provider when you set up the server. Then enter the TCP port number. This should be 9999.

  4. Click Locate collateral to view unused collateral funding transactions available on the connected hardware wallet. Select the address to which you sent 1000 Dash and click Apply. The Collateral address, path, Collateral TX hash and index fields should be filled automatically.

../../../_images/setup-collateral-dmt-ready.png

Dash Masternode Tool with masternode configuration#

Leave DMT open and continue with the next step: installing Dash Core on your VPS.

الخيار 2: إرسال من محفظة داش كور#

افتح محفظة داش كور وانتظر حتى تتم مزامنتها مع الشبكة. يجب أن تبدو مثل هذه عندما تكون جاهزة:

../../../_images/setup-collateral-dashcore.png

متزامن تماما داش كور المحفظة#

Click Window > Console to open the console. Type the following command into the console to generate a new Dash address for the collateral:

getnewaddress
yiFfzbwiN9oneftd7cEfr3kQLRwQ4kp7ue

Take note of the collateral address, since we will need it later. The next step is to secure your wallet (if you have not already done so). First, encrypt the wallet by selecting Settings > Encrypt wallet. You should use a strong, new password that you have never used somewhere else. Take note of your password and store it somewhere safe or you will be permanently locked out of your wallet and lose access to your funds. Next, back up your wallet file by selecting File > Backup Wallet. Save the file to a secure location physically separate to your computer, since this will be the only way you can access our funds if anything happens to your computer. For more details on these steps, see here.

Now send exactly 1000 DASH in a single transaction to the new address you generated in the previous step. This may be sent from another wallet, or from funds already held in your current wallet. Once the transaction is complete, view the transaction in a blockchain explorer by searching for the address. You will need 15 confirmations before you can register the masternode, but you can continue with the next step at this point already: generating your masternode operator key.

../../../_images/setup-collateral-blocks.png

مستكشف Trezor بلوكشين يعرض 15 تأكيدًا لنقل الضمانات#

تتبيت داش كور#

داش كور هو البرنامج وراء كل من محفظة و داش ماسترنود. إذا لم يتم عرض واجهة المستخدم الرسومية ، فإنه يعمل كخادم على (VPS (dashd ، يتم التحكم فيه بواسطة واجهة أوامر بسيطة (dash-cli).

Open PuTTY or a console again and connect using the username and password you just created for your new, non-root user. The following options are available for installing a Dash masternode:

Manual installation#

To manually download and install the components of your Dash masternode, visit the GitHub releases page and copy the link to the latest x86_64-linux-gnu version. Go back to your terminal window and enter the following command, pasting in the address to the latest version of Dash Core by right clicking or pressing Ctrl + V:

cd /tmp
wget https://github.com/dashpay/dash/releases/download/v20.0.4/dashcore-20.0.4-x86_64-linux-gnu.tar.gz

Verify the authenticity of your download by checking its detached signature against the public key published by the Dash Core development team. All releases of Dash are signed using GPG with one of the following keys:

curl https://keybase.io/codablock/pgp_keys.asc | gpg --import
curl https://keybase.io/pasta/pgp_keys.asc | gpg --import
wget https://github.com/dashpay/dash/releases/download/v20.0.4/dashcore-20.0.4-x86_64-linux-gnu.tar.gz.asc
gpg --verify dashcore-20.0.4-x86_64-linux-gnu.tar.gz.asc

Create a working directory for Dash, extract the compressed archive and copy the necessary files to the directory:

mkdir ~/.dashcore
tar xfv dashcore-20.0.4-x86_64-linux-gnu.tar.gz
cp -f dashcore-20.0.4/bin/dashd ~/.dashcore/
cp -f dashcore-20.0.4/bin/dash-cli ~/.dashcore/

قم بإنشاء ملف تكوين باستخدام الأمر التالي:

nano ~/.dashcore/dash.conf

سوف تظهر نافذة المحرر. نحتاج الآن إلى إنشاء ملف تكوين يحدد عدة متغيرات. قم بنسخ النص التالي ولصقه للبدء ، ثم استبدل المتغيرات الخاصة بالتكوين كما يلي:

#----
rpcuser=XXXXXXXXXXXXX
rpcpassword=XXXXXXXXXXXXXXXXXXXXXXXXXXXX
rpcallowip=127.0.0.1
#----
listen=1
server=1
daemon=1
#----
#masternodeblsprivkey=
externalip=XXX.XXX.XXX.XXX
#----

استبدل الحقول التي تحمل علامة XXXXXXX كما يلي:

  • rpcuser: أدخل أي سلسلة من الأرقام أو الحروف ، لا يسمح بالحروف الخاصة

  • rpcpassword: أدخل أي سلسلة من الأرقام أو الحروف ، لا يسمح بالحروف الخاصة

  • externalip: هذا هو عنوان IP الخاص بـ VPS الخاص بك

Leave the masternodeblsprivkey field commented out for now. The result should look something like this:

../../../_images/setup-manual-conf.png

إدخال بيانات المفتاح في dash.conf على ماسترنود#

اضغط على Ctrl + X لإغلاق المحرر و Y و ادخل احفظ الملف. يمكنك الآن بدء تشغيل داش على ماسترنود لتبدأ التزامن مع بلوكشين

~/.dashcore/dashd

You will see a message reading Dash Core server starting.

Add dashd to crontab to make sure it runs every minute to check on your masternode:

crontab -e

Choose nano as your editor and enter the following line at the end of the file:

* * * * * pidof dashd || ~/.dashcore/dashd

اضغط على ادخل لتتأكد من وجود سطر فارغ في نهاية الملف ، ثم اضغط Ctrl + X لإغلاق المحرر و Y و ادخل احفظ الملف. نحتاج الآن إلى الانتظار للحصول على 15 تأكيدًا لمعاملة الضمانات لإكمالها ، والانتظار حتى تنتهي عملية بلوكشين من المزامنة على ماسترنود. يمكنك استخدام الأوامر التالية لمراقبة التقدم

~/.dashcore/dash-cli mnsync status

عند اكتمال المزامنة ، سترى الاستجابة التالية:

{
  "AssetID": 999,
  "AssetName": "MASTERNODE_SYNC_FINISHED",
  "AssetStartTime": 1558596597,
  "Attempt": 0,
  "IsBlockchainSynced": true,
  "IsSynced": true,
  "IsFailed": false
}

Continue with the next step to construct the ProTx transaction required to enable your masternode.

Register your masternode#

The three keys required for the different masternode roles are described briefly under Masternode Concepts in this documentation.

Option 1: Registering from a hardware wallet#

Go back to DMT and ensure that all fields from the previous step are still filled out correctly. Click Generate new for the three private keys required for a masternode:

  • Owner private key

  • Operator private key

  • Voting private key

../../../_images/setup-dmt-full.png

Dash Masternode Tool ready to register a new masternode#

Then click Register masternode. Optionally specify a different Payout address and/or Operator reward, then click Continue. Select Remote Dash RPC Node (automatic method). (See here for documentation on using your own local RPC node.) and confirm the following two messages:

../../../_images/setup-dmt-send.png
../../../_images/setup-dmt-sent.png

Dash Masternode Tool confirmation dialogs to register a masternode#

The BLS private key must be entered in the dash.conf file on the masternode. This allows the masternode to watch the blockchain for relevant Pro*Tx transactions, and will cause it to start serving as a masternode when the signed ProRegTx is broadcast by the owner, as we just did above. Log in to your masternode using ssh or PuTTY and edit the configuration file as follows:

nano ~/.dashcore/dash.conf

The editor appears with the existing masternode configuration. Add or uncomment this lines in the file, replacing the key with your BLS private key generated above:

masternodeblsprivkey=24c1fa3c22c6ea6b1cc68a37be18acb51042b19465fe0a26301c8717bf939805

Press enter to make sure there is a blank line at the end of the file, then press Ctrl + X to close the editor and Y and Enter save the file. Note that providing a masternodeblsprivkey enables masternode mode, which will automatically force the txindex=1, peerbloomfilters=1, and prune=0 settings necessary to provide masternode service. We now need to restart the masternode for this change to take effect. Enter the following commands, waiting a few seconds in between to give Dash Core time to shut down:

~/.dashcore/dash-cli stop
sleep 15
~/.dashcore/dashd

At this point you can monitor your masternode by entering ~/.dashcore/dash-cli masternode status or using the Get status function in DMT. The final result should appear as follows:

../../../_images/setup-dash-cli-start.png

dash-cli masternode status output showing successfully registered masternode#

في هذه المرحلة ، يمكنك الخروج من الخادم بأمان عن طريق كتابة exit . تهانينا! الخاص بك ماسترنود قيد التشغيل الآن.

Option 2: Registering from Dash Core wallet#

Identify the funding transaction#

If you used an address in Dash Core wallet for your collateral transaction, you now need to find the txid of the transaction. Click Window > Console and enter the following command:

masternode outputs

This should return a string of characters similar to the following:

{
"16347a28f4e5edf39f4dceac60e2327931a25fdee1fb4b94b63eeacf0d5879e3-1",
}

The first long string is your collateralHash, while the last number is the collateralIndex.

Generate a BLS key pair#

A public/private BLS key pair is required to operate a masternode. The private key is specified on the masternode itself, and allows it to be included in the deterministic masternode list once a provider registration transaction with the corresponding public key has been created.

If you are using a hosting service, they may provide you with their public key, and you can skip this step. If you are hosting your own masternode or have agreed to provide your host with the BLS private key, generate a BLS public/private keypair in Dash Core by clicking Tools > Console and entering the following command:

bls generate

{
  "secret": "395555d67d884364f9e37e7e1b29536519b74af2e5ff7b62122e62c2fffab35e",
  "public": "99f20ed1538e28259ff80044982372519a2e6e4cdedb01c96f8f22e755b2b3124fbeebdf6de3587189cf44b3c6e7670e",
  "scheme": "legacy"
}

These keys are NOT stored by the wallet and must be kept secure, similar to the value provided in the past by the masternode genkey command.

Add the private key to your masternode configuration#

The public key will be used in following steps. The private key must be entered in the dash.conf file on the masternode. This allows the masternode to watch the blockchain for relevant Pro*Tx transactions, and will cause it to start serving as a masternode when the signed ProRegTx is broadcast by the owner (final step below). Log in to your masternode using ssh or PuTTY and edit the configuration file as follows:

nano ~/.dashcore/dash.conf

The editor appears with the existing masternode configuration. Add or uncomment this line in the file, replacing the key with your BLS private key generated above:

masternodeblsprivkey=395555d67d884364f9e37e7e1b29536519b74af2e5ff7b62122e62c2fffab35e

Press enter to make sure there is a blank line at the end of the file, then press Ctrl + X to close the editor and Y and Enter save the file. Note that providing a masternodeblsprivkey enables masternode mode, which will automatically force the txindex=1, peerbloomfilters=1, and prune=0 settings necessary to provide masternode service. We now need to restart the masternode for this change to take effect. Enter the following commands, waiting a few seconds in between to give Dash Core time to shut down:

~/.dashcore/dash-cli stop
sleep 15
~/.dashcore/dashd

We will now prepare the transaction used to register the masternode on the network.

Prepare a ProRegTx transaction#

A pair of BLS keys for the operator were already generated above, and the private key was entered on the masternode. The public key is used in this transaction as the operatorPubKey.

First, we need to get a new, unused address from the wallet to serve as the owner key address (ownerKeyAddr). This is not the same as the collateral address holding 1000 Dash. Generate a new address as follows:

getnewaddress

yfgxFhqrdDG15ZWKJAN6dQvn6dZdgBPAip

This address can also be used as the voting key address (votingKeyAddr). Alternatively, you can specify an address provided to you by your chosen voting delegate, or simply generate a new voting key address as follows:

getnewaddress

yfRaZN8c3Erpqj9iKnmQ9QDBeUuRhWV3Mg

Then either generate or choose an existing address to receive the owner's masternode payouts (payoutAddress). It is also possible to use an address external to the wallet:

getnewaddress

yjZVt49WsQd6XSrPVAUGXtJccxviH9ZQpN

You can also optionally generate and fund another address as the transaction fee source (feeSourceAddress). If you selected an external payout address, you must specify a fee source address.

Either the payout address or fee source address must have enough balance to pay the transaction fee, or the register_prepare transaction will fail.

The private keys to the owner and fee source addresses must exist in the wallet submitting the transaction to the network. If your wallet is protected by a password, it must now be unlocked to perform the following commands. Unlock your wallet for 5 minutes:

walletpassphrase yourSecretPassword 300

We will now prepare an unsigned ProRegTx special transaction using the protx register_prepare command. This command has the following syntax:

protx register_prepare collateralHash collateralIndex ipAndPort ownerKeyAddr
  operatorPubKey votingKeyAddr operatorReward payoutAddress (feeSourceAddress)

تحذير

After v19 hard fork activation, protx register_prepare_legacy must be used if a legacy scheme BLS key is being used to register a masternode. It's recommended to instead generate a new basic scheme BLS key where possible. This can be done by following the Generate a BLS key pair instructions.

Open a text editor such as notepad to prepare this command. Replace each argument to the command as follows:

  • collateralHash: The txid of the 1000 Dash collateral funding transaction

  • collateralIndex: The output index of the 1000 Dash funding transaction

  • ipAndPort: Masternode IP address and port, in the format x.x.x.x:yyyy

  • ownerKeyAddr: The new Dash address generated above for the owner/voting address

  • operatorPubKey: The BLS public key generated above (or provided by your hosting service)

  • votingKeyAddr: The new Dash address generated above, or the address of a delegate, used for proposal voting

  • operatorReward: The percentage of the block reward allocated to the operator as payment

  • payoutAddress: A new or existing Dash address to receive the owner's masternode rewards

  • feeSourceAddress: An (optional) address used to fund ProTx fee. payoutAddress will be used if not specified.

Note that the operator is responsible for specifying their own reward address in a separate update_service transaction if you specify a non-zero operatorReward. The owner of the masternode collateral does not specify the operator's payout address.

Example (remove line breaks if copying):

protx register_prepare
  16347a28f4e5edf39f4dceac60e2327931a25fdee1fb4b94b63eeacf0d5879e3
  1
  45.76.230.239:19999
  yfgxFhqrdDG15ZWKJAN6dQvn6dZdgBPAip
  99f20ed1538e28259ff80044982372519a2e6e4cdedb01c96f8f22e755b2b3124fbeebdf6de3587189cf44b3c6e7670e
  yfRaZN8c3Erpqj9iKnmQ9QDBeUuRhWV3Mg
  0
  yjZVt49WsQd6XSrPVAUGXtJccxviH9ZQpN
  yR83WsikBaBaNusTnHZf28kAcL8oVmp1TE

Output:

{
  "tx": "030001000175c9d23c2710798ef0788e6a4d609460586a20e91a15f2097f56fc6e007c4f8e0000000000feffffff01a1949800000000001976a91434b09363474b14d02739a327fe76e6ea12deecad88ac00000000d1010000000000e379580dcfea3eb6944bfbe1de5fa2317932e260acce4d9ff3ede5f4287a34160100000000000000000000000000ffff2d4ce6ef4e1fd47babdb9092489c82426623299dde76b9c72d9799f20ed1538e28259ff80044982372519a2e6e4cdedb01c96f8f22e755b2b3124fbeebdf6de3587189cf44b3c6e7670ed1935246865dce1accce6c8691c8466bd67ebf1200001976a914fef33f56f709ba6b08d073932f925afedaa3700488acfdb281e134504145b5f8c7bd7b47fd241f3b7ea1f97ebf382249f601a0187f5300",
  "collateralAddress": "yjSPYvgUiAQ9AFj5tKFA8thFLoLBUxQERb",
  "signMessage": "yjZVt49WsQd6XSrPVAUGXtJccxviH9ZQpN|0|yfgxFhqrdDG15ZWKJAN6dQvn6dZdgBPAip|yfRaZN8c3Erpqj9iKnmQ9QDBeUuRhWV3Mg|ad5f82257bd00a5a1cb5da1a44a6eb8899cf096d3748d68b8ea6d6b10046a28e"
}

Next we will use the collateralAddress and signMessage fields to sign the transaction, and the output of the tx field to submit the transaction.

Sign the ProRegTx transaction#

We will now sign the content of the signMessage field using the private key for the collateral address as specified in collateralAddress. Note that no internet connection is required for this step, meaning that the wallet can remain disconnected from the internet in cold storage to sign the message. In this example we will again use Dash Core, but it is equally possible to use the signing function of a hardware wallet. The command takes the following syntax:

signmessage collateralAddress signMessage

Example:

signmessage yjSPYvgUiAQ9AFj5tKFA8thFLoLBUxQERb yjZVt49WsQd6XSrPVAUGXtJccxviH9ZQpN|0|yfgxFhqrdDG15ZWKJAN6dQvn6dZdgBPAip|yfRaZN8c3Erpqj9iKnmQ9QDBeUuRhWV3Mg|ad5f82257bd00a5a1cb5da1a44a6eb8899cf096d3748d68b8ea6d6b10046a28e

Output:

II8JvEBMj6I3Ws8wqxh0bXVds6Ny+7h5HAQhqmd5r/0lWBCpsxMJHJT3KBcZ23oUZtsa6gjgISf+a8GzJg1BfEg=

Submit the signed message#

We will now submit the ProRegTx special transaction to the blockchain to register the masternode. This command must be sent from a Dash Core wallet holding a balance on either the feeSourceAddress or payoutAddress, since a standard transaction fee is involved. The command takes the following syntax:

protx register_submit tx sig

أين:

  • tx: The serialized transaction previously returned in the tx output field from the protx register_prepare command

  • sig: The message signed with the collateral key from the signmessage command

Example:

protx register_submit 030001000175c9d23c2710798ef0788e6a4d609460586a20e91a15f2097f56fc6e007c4f8e0000000000feffffff01a1949800000000001976a91434b09363474b14d02739a327fe76e6ea12deecad88ac00000000d1010000000000e379580dcfea3eb6944bfbe1de5fa2317932e260acce4d9ff3ede5f4287a34160100000000000000000000000000ffff2d4ce6ef4e1fd47babdb9092489c82426623299dde76b9c72d9799f20ed1538e28259ff80044982372519a2e6e4cdedb01c96f8f22e755b2b3124fbeebdf6de3587189cf44b3c6e7670ed1935246865dce1accce6c8691c8466bd67ebf1200001976a914fef33f56f709ba6b08d073932f925afedaa3700488acfdb281e134504145b5f8c7bd7b47fd241f3b7ea1f97ebf382249f601a0187f5300 II8JvEBMj6I3Ws8wqxh0bXVds6Ny+7h5HAQhqmd5r/0lWBCpsxMJHJT3KBcZ23oUZtsa6gjgISf+a8GzJg1BfEg=

Output:

aba8c22f8992d78fd4ff0c94cb19a5c30e62e7587ee43d5285296a4e6e5af062

Your masternode is now registered and will appear on the Deterministic Masternode List after the transaction is mined to a block. You can view this list on the Masternodes -> DIP3 Masternodes tab of the Dash Core wallet, or in the console using the command protx list valid, where the txid of the final protx register_submit transaction identifies your masternode.

At this point you can go back to your terminal window and monitor your masternode by entering ~/.dashcore/dash-cli masternode status or using the Get status function in DMT.

في هذه المرحلة ، يمكنك الخروج من الخادم بأمان عن طريق كتابة exit . تهانينا! الخاص بك ماسترنود قيد التشغيل الآن.

Option 3: Registering from Dash Electrum wallet#

Dash Electrum supports registering and managing masternodes. Details can be found on the Electrum - Advanced Functions page. If combined with Electrum's multisig features the masternode collateral can be stored in a multisig wallet for increased security flexibility.

تحذير

Always exercise caution when using multisig accounts and verify that each mnemonic is backed up appropriately. See this page for the Dash Electrum documentation demonstrating how to configure a masternode using a multisig collateral.