维护#

主节点需要定期维护，以确保您不会从支付队列中退出。这包括及时安装达世币的更新版本，以及保持服务器的安全性和性能。此外，主节点应该对提案进行投票，并为了网络的利益和他们所持有的达世币的价值而执行其他任务。

主节点软件升级#

The Dash Core software requires regular updates in order to remain consistent with the current network consensus. Follow the procedure described below to manually update your masternode. If you are still using the legacy dashman installer, see the legacy update documentation here.

Manual update#

如果手动升级，用 ssh 或 PuTTY 登录你的服务器。如果你的计划任务里面有定时重启 dashd 的记录，执行``crontab -e`` 在行首添加”#“字符来将对应行注释掉。应该看起来像这样：

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

然后停止 Dash：

~/.dashcore/dash-cli stop

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.2/dashcore-20.0.2-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:

Alexander Block (codablock) with the key 63A9 6B40 6102 E091, verifiable here on Keybase
Pasta (pasta) with the key 5252 7BED ABE8 7984, verifiable here on Keybase

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.2/dashcore-20.0.2-x86_64-linux-gnu.tar.gz.asc
gpg --verify dashcore-20.0.2-x86_64-linux-gnu.tar.gz.asc

解压缩然后复制新文件到目录：

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

重新启动达世币:

~/.dashcore/dashd

You will see a message reading “Dash Core server starting”. The Dash software on the masternode is now updated.

Updating Masternode Information#

Periodically, it may be necessary to update masternode information if any information relating to the owner or operator changes. Examples may include a change in IP address, change in owner/operator payout address or changes to the nominated voting/operator keys. It is also possible to revoke a masternode’s registered status (in the event of a security breach, for example) to force both owner and operator to update their details.

Changing the BLS operator key or creating a new ProTx based on the same collateral transaction will reset your position in the payment queue. Changing your IP address or making changes to the voting or various payout addresses will not reset your position in the payment queue.

ProUpServTx#

A Provider Update Service Transaction (ProUpServTx) is used to update information relating to the operator. An operator can update the IP address and port fields of a masternode entry. If a non-zero operatorReward was set in the initial ProRegTx, the operator may also set the operatorPayoutAddress field in the ProUpServTx. If operatorPayoutAddress is not set and operatorReward is non-zero, the owner gets the full masternode reward. A ProUpServTx can be created from DMT by clicking the Update service button, or from Dash Core using the following syntax:

protx update_service proTxHash ipAndPort operatorKey (operatorPayoutAddress feeSourceAddress)

其中：

proTxHash: The transaction id of the initial ProRegTx
ipAndPort: IP and port in the form “ip:port”
operatorKey: The operator BLS private key associated with the registered operator public key
operatorPayoutAddress (optional): The address used for operator reward payments. Only allowed when the ProRegTx had a non-zero operatorReward value. Enter "" to use the last on-chain operator payout address, or as a placeholder when specifying a feeSourceAddress.
feeSourceAddress (optional): An address used to fund ProTx fee. operatorPayoutAddress will be used if not specified.

Example:

protx update_service d6ec9a03e1251ac8c34178f47b6d763dc4ea6d96fd6eddb3c7aae2359e0f474a 140.82.59.51:10002 4308daa8de099d3d5f81694f6b618381e04311b9e0345b4f8b025392c33b0696 yf6Cj6VcCfDxU5yweAT3NKKvm278rVbkhu

fad61c5f21cf3c0832f782c1444d3d2e2a8dbff39c5925c38033730e64ecc598

The masternode is now removed from the PoSe-banned list, and the IP:port and operator reward addresses are updated.

ProUpRegTx#

A Provider Update Registrar Transaction (ProUpRegTx) is used to update information relating to the owner. An owner can update the operator’s BLS public key (e.g. to nominate a new operator), the voting address and their own payout address. A ProUpRegTx can be created from DMT by clicking the Update operator key, Update voting key or Update payout addr. buttons, or from Dash Core using the following syntax:

protx update_registrar proTxHash operatorKeyAddr votingKeyAddr payoutAddress (feeSourceAddress)

警告

After v19 hard fork activation, protx update_registrar_legacy must be used if a legacy scheme BLS key is being used to registrar update a masternode.

其中：

proTxHash: The transaction id of the initial ProRegTx
operatorKeyAddr: An updated BLS public key, or "" to use the last on-chain operator key
votingKeyAddr: An updated voting key address, or "" to use the last on-chain voting key
payoutAddress: An updated Dash address for owner payments, or "" to use the last on-chain operator key
feeSourceAddress (optional): An address used to fund ProTx fee. PayoutAddress will be used if not specified.

Example to update payout address:

protx update_registrar cedce432ebabc9366f5eb1e3abc219558de9fbd2530a13589b698e4bf917b8ae "" "" yi5kVoPQQ8xaVoriytJFzpvKomAQxg6zea

ProUpRevTx#

A Provider Update Revocation Transaction (ProUpRevTx) is used by the operator to terminate service or signal the owner that a new BLS key is required. It will immediately put the masternode in the PoSe-banned state. The owner must then issue a ProUpRegTx to set a new operator key. After the ProUpRegTx is mined to a block, the new operator must issue a ProUpServTx to update the service-related metadata and clear the PoSe- banned state (revive the masternode). A ProUpRevTx can be created from DMT by clicking the Revoke operator button, or from Dash Core using the following syntax:

protx revoke proTxHash operatorKey reason (feeSourceAddress)

其中：

proTxHash: The transaction id of the initial ProRegTx
operatorKey: The operator BLS private key associated with the registered operator public key
reason: Integer value indicating the revocation reason
feeSourceAddress (optional): An address used to fund ProTx fee. operatorPayoutAddress will be used if not specified.

Example:

protx revoke 9f5ec7540baeefc4b7581d88d236792851f26b4b754684a31ee35d09bdfb7fb6 565950700d7bdc6a9dbc9963920bc756551b02de6e4711eff9ba6d4af59c0101 0

Proof of Service Bans#

If your masternode fails to provide service to the network in accordance with the current consensus rules, it will receive a Proof of Service Ban. If your masternode is in the POSE_BANNED status, you should check the following settings are configured correctly:

Ensure you are running the latest version of Dash
Ensure your masternode has sufficient memory, swap, processing power and hard drive space
Ensure you are fully synced to the correct blockheight, and that you are on the correct chain and not forked off
Ensure that a BLS private key is specified using the masternodeblsprivkey option in the masternode’s dash.conf file
Ensure that the BLS private key on the masternode is unique on the network and not shared with any other masternodes
Ensure that the BLS private key on the masternode corresponds to the BLS public key registered on the blockchain in the ProRegTx or ProUpRegTx
Ensure that the externalip (and port if using testnet) are specified correctly and not blocked by a firewall or port forwarding service

Once you are certain these settings are correct, you can update your service status on the network and return to the valid set of masternodes by creating a ProUpServTx. Monitor your masternode closely using masternode status and/or the debug.log file after restoring service. This information can help you pinpoint the specific misconfiguration that is causing the masternode to be banned. The masternode will be banned again if it continues to fail to provide service.

DashCentral 投票，验证和监测#

DashCentral是由社区成员Rango管理的以支持社区为主的网站。它已成为一个 事实上的 网站，用来讨论预算提案，以方便从图形用户界面投票，但它也提供了监测主节点的功能。

将您的主节点添加到DashCentral#

Dashcentral允许您在浏览器的舒适环境下对提案进行投票。在完成注册后，转到主节点页面并单击 现在添加主节点 按钮。在以下屏幕上输入您的钱包地址:

../../../_images/maintenance-dc-add-masternode.png — 向DashCentral添加一个主节点#

单击 添加主节点 。您的主节点现在已经被添加到DashCentral。

从DashCentral启用投票#

在 投票私钥 下单击编辑来输入您的主节点私钥，以便通过DashCentral 网站界面进行投票。输入投票密码(与登录密码不同，但同样重要需要记住！)，并在以下屏幕上输入私钥(在主节点上的dash.conf文件中使用的相同的密钥):

../../../_images/maintenance-dc-add-privkey.png — 将投票私钥添加到DashCentra#

需要注意的是，激活您的主节点的私钥与存储1000个达世币的钱包地址的私钥无关。这些密钥可用于代表主节点发送命令，如投票，但不能用于获取保证金。这些密钥在您的设备上是被加密的，且从未以纯文本形式存储在DashCentral服务器上。一旦您输入了密钥，单击 在服务器上存储加密的投票私钥 。您现在可以从DashCentral 网站界面对提案进行投票。

验证所有权#

您也可以从您的地址发出一条消息来验证您的主节点对DashCentral的所有权。在 所有权 下单击 未验证 ，将出现以下屏幕:

../../../_images/maintenance-dc-verify.png — 验证您的主节点对DashCentral的所有权#

有关如何使用软件钱包保证金地址的说明将会显示出来。如果您正在使用除Trezor以外的硬件钱包，您则需要使用DMT应用程序对地址进行签名。如果您正在使用Trezor硬件钱包，转到您的Trezor wallet，复制钱包地址，然后单击 签名和验证 。以下屏幕将会出现，您可以在其中输入DashCentral提供的信息和您希望签名的地址:

../../../_images/maintenance-dc-sign.png — 从Trezor钱包签名信息#

单击签名，在您的Trezor设备上确认并输入您的PIN码来签名该信息。信息签名将出现在签名框中。复制此签名并将其粘贴到DashCentral上的方框中，并单击 验证所有权 。验证工作现已完成。

../../../_images/maintenance-dc-verified.png — 主节点所有权已被成功验证#

安装DashCentral监测脚本#

DashCentral提供一项监测您的主节点的服务，它会在系统崩溃时自动重新启动dashd，并在发生错误时发送电子邮件。转到账户设置页面，并生成一个新的API密钥，必要时向您的帐户添加一个PIN码。滚动到以下屏幕:

../../../_images/maintenance-dc-monitoring.png — 设置DashCentral监测脚本#

右键单击并选择 复制链接地址 将链接复制到DashCentral脚本的当前版本。打开PuTTY并连接到您的主节点，然后键入:

wget https://www.dashcentral.org/downloads/dashcentral-updater-v6.tgz

必要时用当前版本的DashCentral更新程序替换链接。使用以下命令解压压缩的归档文件:

tar xvzf dashcentral-updater-v6.tgz

通过键入查看您的主节点配置的详细信息:

cat .dashcore/dash.conf

复制 rpcuser 和 rpcpassword 的值。然后通过键入来编辑DashCentral配置:

nano dashcentral-updater/dashcentral.conf

根据您的系统替换 api_key、您的主节点的钱包地址、 rpc_user、 rpc_password、 daemon_binary 和 daemon_datadir 的值。在常见的配置中， lwhite 是Linux用户的名称，可能如下所示：

../../../_images/maintenance-dc-update-config.png — DashCentral更新程序配置文件#

################
# dashcentral-updater configuration
################

our %settings = (
    # Enter your DashCentral api key here
    'api_key' => 'api_key_from_dashcentral'
);

our %masternodes = (
    'masternode_collateral_address' => {
        'rpc_host'           => 'localhost',
        'rpc_port'           => 9998,
        'rpc_user'           => 'rpc_user_from_dash.conf',
        'rpc_password'       => 'rpc_password_from_dash.conf',
        'daemon_autorestart' => 'enabled',
        'daemon_binary'      => '/home/<username>/.dashcore/dashd',
        'daemon_datadir'     => '/home/<username>/.dashcore'
    }
);

按 Ctrl + X 退出，确认您想要使用 Y ** 保存，然后按下 **Enter 键。通过运行DashCentral脚本测试您的配置，然后查看网站。如果测试成功，您会看到更新已被发送:

dashcentral-updater/dcupdater

../../../_images/maintenance-dc-update.png — 手动测试DashCentral更新程序#

../../../_images/maintenance-dc-success.png — DashCentral更新程序已成功地将数据发送到DashCentral站点#

一旦您验证了您的配置有效，我们就可以在您的系统上编辑crontab，以便将dcudater脚本安排为每2分钟运行一次。这允许系统在发生故障时为您提供早期警告，甚至会在dashd守护进程挂起或崩溃将其重新启动。这是一个有效的方法，以确保您不会从支付队列中掉线。键入以下命令:

crontab -e

Select an editor if necessary and add the following line at the end of your crontab, replacing lwhite with your username on your system:

*/2 * * * * /home/lwhite/dashcentral-updater/dcupdater

../../../_images/maintenance-dc-crontab.png — 编辑crontab以自动运行DashCentral更新程序#

按 Ctrl + X 退出，确认您想要使用 Y 保存，然后按下 Enter 键。现在，dcupdater脚本将每两分钟运行一次，并在必要时重新启动dashd，在发生错误时给您发送电子邮件。

主节点监测工具#

几个由社区成员操作的站点可用于监测与主节点网络有关的关键信息和统计数据。

区块浏览器#

由于达世币是一个公有区块链，所以可以使用区块浏览器查看任何达世币钱包地址的余额，以及检查在任何给定块中输入的交易。每个唯一的交易也可以通过txid进行搜索。可以使用多种不同区块浏览器查看达世币网络。

Blockchair offers a block explorer with detailed visualizations to analyse the Dash blockchain.
CryptoID 提供一个达世币区块链浏览器和一个功能来查看和浏览达世币主节点。
BitInfoCharts 提供了价格统计和信息的页面和区块链浏览器。
CoinCheckup 提供了包括达世币在内的大多数区块链的一系列统计信息和数据。
Dash.org includes a blockchain explorer at explorer.dash.org and insight.dash.org.
Trezor operates a blockchain explorer powered by a Dash fork of insight, an advanced blockchain API tool

达世币主节点工具#

Bertrand256/dash-masternode-tool

由社区成员Bertrand256编写和维护的Dash Masterode工具(DMT)允许您从所有主要硬件钱包，如Trezor、Ledger和KeepKey，激活主节点。它还有在不影响保证金的情况下对提案进行投票和提取主节点区块奖励。

DASH Ninja#

https://www.dashninja.pl

由论坛成员和Dash Core开发人员elbereth运营的DASH Ninja提供了关于在主节点网络中采用不同版本达世币的关键统计数据。它还提供了多个如监测达世币管理、主节点奖励时间和主节点地理分布的功能，以及提供了一个简单的区块链浏览器。

DashCentral#

https://www.dashcentral.org

DashCentral, operated by forum member rango, offers an advanced service to monitor masternodes and vote on budget proposals through an advanced web interface.

Masternode.me#

https://stats.masternode.me

Masternode.me, operated by Dash community member moocowmoo, offers sequential reports on the price, generation rate, blockchain information and some information on masternodes.

达世币主节点信息#

http://178.254.23.111/~pub/Dash/Dash_Info.html

由论坛成员和Dash Core 开发人员 Corning运营的网站，提供了达世币主节点网络的许多关键统计信息的可视化表示，包括总主节点数关于时间、价格信息和网络分布的图表。