Dash masternode dashcore installing
- Thread starter Rul
- Start date
If you are installing for a new masternode, I assume you are because you posted in the masternode guides thread, use this script to install it properly for hassle free operation.
www.dash.org
DASH Masternode Zeus (replacement for dashman)
Dear All, This is a dedicated thread for DASH Masternode Zeus (DMZ). It is an alternative to the aging DASHMAN. It installs a new masternode on a Ubuntu VPS according to my guide using a simple to use TUI. It is available from https://github.com/kxcd/Masternode-Zeus You can clone it and run...
Yeah, I saw this guide. But I already start set up with official instruction. Does dashd is dash blockchain? I need to understand if I have dash blockchain on my server or no.If you are installing for a new masternode, I assume you are because you posted in the masternode guides thread, use this script to install it properly for hassle free operation.
DASH Masternode Zeus (replacement for dashman)
Dear All, This is a dedicated thread for DASH Masternode Zeus (DMZ). It is an alternative to the aging DASHMAN. It installs a new masternode on a Ubuntu VPS according to my guide using a simple to use TUI. It is available from https://github.com/kxcd/Masternode-Zeus You can clone it and run...
Yes, dashd is a full node, so it will keep a copy of the entire blockchain, about 50GB.
Even if you started with the official guide, you can still wipe and start over with the Zeus, all you need to transfer over is the BLS key. You will find it much more stable than the official instructions.
After a full sync the Dash blockchain shows up to blk00195 and up to rev00195 in the blocks folder inside your Dash data folder.
If you have installed WINSCP, you can login to your masternode from time to time to check the blocks folder in order to see how far your sync is.
My experience is that a full sync could take most of the day.
Don't forget to install sentinel, don't forget about the firewall part and also don't forget the cronjob part (these are all mentioned in the official instruction).
After your registered your masternode successfully, you can add it to Dash Central.
Masternode monitoring and budget voting - DashCentral.org
At DashCentral, you can monitor the uptime of your DASH masternodes and perform votes on budget proposals easy and comfortable
www.dashcentral.org
I use Dash Central to vote on budget proposals, keep an eye on any possible PoSe scores of my masternodes and to get notifications about incoming masternode payments. Also Dash Central has a monitor and automatic restart option, for when your masternode crashes.
Welcome new masternode owner.
Last edited:
and all completely unnecessary and not trustless. Simply use the Masternode Zeus and there is no need for some third party hack to monitor the node and restart it when it crashes, because it won't be crashing.After a full sync the Dash blockchain shows up to blk00195 and up to rev00195 in the blocks folder inside your Dash data folder.
If you have installed WINSCP, you can login to your masternode from time to time to check the blocks folder in order to see how far your sync is.
My experience is that a full sync could take most of the day.
Don't forget to install sentinel, don't forget about the firewall part and also don't forget the cronjob part (these are all mentioned in the official instruction).
After your registered your masternode successfully, you can add it to Dash Central.
Masternode monitoring and budget voting - DashCentral.org
At DashCentral, you can monitor the uptime of your DASH masternodes and perform votes on budget proposals easy and comfortable
I use Dash Central to vote on budget proposals, keep an eye on any possible PoSe scores of my masternodes and to get notifications about incoming masternode payments. Also Dash Central has a monitor and automatic restart option, for when your masternode crashes.
Welcome new masternode owner.
I decided to use Masternode Zeus. How can I do this successfully if now I am stuck on Dash Core installing step? I don;t have any memory to use Zeus script now. Should I delete all unneeded files? From what step do I need to tape this 3 commands for Zeus? I did "set up operating system" and "send collateral" steps.
From the VPS server in the dash.conf file just copy the BLS key to notepad. Then go to the VPS admin panel (in the browser) and select to reinstall the OS, choose Ubuntu 21 LTS, not 22! and reimage the VPS. From there follow the Zeus instructions, you start by logging in as root again. When the zeus asks for the BLS key, just paste it back in.
I am trying to register my masternode in DashMasternodeTool and I keep getting this issue HwSessionInfo' object has no attribute 'hw_disconnect'. How can I fix this?
I recommend against using the DMT, are you able to export the private keys from there? Ideally, you want to keep the owner, voting and payout keys in a Core QT wallet. The collateral remains on the trezor/ledger. Refer to this guide for some details.
How to create the perfect Masternode
So, I've been talking to some people in the community and it seems some MNOs have set-up their Masternodes in a way that makes operating them a real pain the ass and can also reduce their privacy. This guide is to help you make some choices on where to keep your keys to make operating your...
Get the Core QT wallet from the official Das dot org website and install it, let it sync the chain, takes about a day to do it.
I have my Dash Core installed on computer. But for what? How is it connected to my node? All my funds are on ledger.I recommend against using the DMT, are you able to export the private keys from there? Ideally, you want to keep the owner, voting and payout keys in a Core QT wallet. The collateral remains on the trezor/ledger. Refer to this guide for some details.
How to create the perfect Masternode
So, I've been talking to some people in the community and it seems some MNOs have set-up their Masternodes in a way that makes operating them a real pain the ass and can also reduce their privacy. This guide is to help you make some choices on where to keep your keys to make operating your...
Get the Core QT wallet from the official Das dot org website and install it, let it sync the chain, takes about a day to do it.
How can I register my masternode if I installed Masternode Zeus and I don;t have bls key and any private key? I just have Zeus masternode installed on my server.I recommend against using the DMT, are you able to export the private keys from there? Ideally, you want to keep the owner, voting and payout keys in a Core QT wallet. The collateral remains on the trezor/ledger. Refer to this guide for some details.
How to create the perfect Masternode
So, I've been talking to some people in the community and it seems some MNOs have set-up their Masternodes in a way that makes operating them a real pain the ass and can also reduce their privacy. This guide is to help you make some choices on where to keep your keys to make operating your...
Get the Core QT wallet from the official Das dot org website and install it, let it sync the chain, takes about a day to do it.
This is a bit confusing, because I don't know what part of the process you are in. Do you have the 1000 Dash collateral already? Ideally, the rough outline of the process is as follows.
- Send 1000 Dash exactly to an address in your Trezor or Ledger hardware wallet.
- In the Core QT Desktop wallet, issue the bls generate command this will create two keys, copy paste them to notepad. The secret key is also copied to the masternode server, the DMZ will ask for it when installing, or you can later replace using the edit dash.conf option.
- In the Core wallet, issue protx register_prepare and observe the required keys.
- To continue, click on the Receiving tab in the core wallet and for the label type in something similar to MN_Owner now press the create receiving address button. Repeat this process for the MN_Voting key and the MN_Payout key.
- Back in the Console, fill out the protx register_prepare command using the IP address of the VPS server (and port (9999)), the BLS key, the 3 addresses you just made and an address in your wallet that has a small amount of Dash for the fee. eg 0.0001 Dash.
- Then copy/paste the output it asks you to sign the message with your collateral address, this is something you need to do with the hardware wallet, instructions on how to do this come with the wallet.
- Once the message is signed, you can continue in the core wallet with protx register_submit this will complete the process and get the node online.
I am on step 3. Should I write "register prepare" in console or where? Because console answer is "Method not found".
Hello one more time!
I am on step 5 and I keep getting "No funds at specified address ************* (code -32603)". But there are funds which should be enough for the fee. How can I fix that?
We keep getting answer that on our payoutAddress which will be used as feeSourceAddress as well don;t have funds. But it has. Also we don;t understand what
(feeSourceAddress) - The private key belonging to this address must be known in your wallet. - means?
Last edited:
Source : https://docs.dash.org/en/stable/masternodes/setup.html#register-your-masternode
If you have funds in the payoutaddress and you want to use those funds to pay for this protx transaction then it should be like this :
protx register_prepare collateralHash collateralIndex ipAndPort ownerKeyAddr operatorPubKey votingKeyAddr operatorReward payoutAddress
You can also add a new address (feesourceAddress) inside your DashCore wallet, put some funds into it and pay the protx transaction fee from that address by using the optional feeSourceAddress, the protx command then looks like this :
protx register_prepare collateralHash collateralIndex ipAndPort ownerKeyAddr operatorPubKey votingKeyAddr operatorReward payoutAddress feeSourceAddress
When registering from the DashCore wallet :
The feeSourceAdress needs to be known inside the wallet that you are using to create the protx command with. And i suspect the same for the payoutAddress, if you plan to have the protx transaction fee paid from there. Both receiving addresses in that case need to be present in the DashCore wallet that you are using to create the protx command with. So that the DashCore wallet can collect the protx transaction fee.
In my experience it is best to just create a new receiving address in your DashCore wallet (debug console : getnewaddress), name it feeSourceAddress (File-Receiving addresses-add name) and sent some small Dash funds to it and then create the following command on your DashCore wallet :
protx register_prepare collateralHash collateralIndex ipAndPort ownerKeyAddr operatorPubKey votingKeyAddr operatorReward payoutAddress feeSourceAddress
And then follow the rest of the setup guide.
This way, the DashCore wallet can use the funds inside its own wallet to create the protx transaction and you can use payoutAddress to receive masternode payments externally (either on another DashCore wallet or on a hardware wallet).
Last edited:
Thank you! It helped me!
Source : https://docs.dash.org/en/stable/masternodes/setup.html#register-your-masternode
If you have funds in the payoutaddress and you want to use those funds to pay for this protx transaction then it should be like this :
protx register_prepare collateralHash collateralIndex ipAndPort ownerKeyAddr operatorPubKey votingKeyAddr operatorReward payoutAddress
You can also add a new address (feesourceAddress) inside your DashCore wallet, put some funds into it and pay the protx transaction fee from that address by using the optional feeSourceAddress, the protx command then looks like this :
protx register_prepare collateralHash collateralIndex ipAndPort ownerKeyAddr operatorPubKey votingKeyAddr operatorReward payoutAddress feeSourceAddress
When registering from the DashCore wallet :
The feeSourceAdress needs to be known inside the wallet that you are using to create the protx command with. And i suspect the same for the payoutAddress, if you plan to have the protx transaction fee paid from there. Both receiving addresses in that case need to be present in the DashCore wallet that you are using to create the protx command with. So that the DashCore wallet can collect the protx transaction fee.
In my experience it is best to just create a new receiving address in your DashCore wallet (debug console : getnewaddress), name it feeSourceAddress (File-Receiving addresses-add name) and sent some small Dash funds to it and then create the following command on your DashCore wallet :
protx register_prepare collateralHash collateralIndex ipAndPort ownerKeyAddr operatorPubKey votingKeyAddr operatorReward payoutAddress feeSourceAddress
And then follow the rest of the setup guide.
This way, the DashCore wallet can use the funds inside its own wallet to create the protx transaction and you can use payoutAddress to receive masternode payments externally (either on another DashCore wallet or on a hardware wallet).
Which wallets will you reccomend to sign a message in? If my funds are on Ledger Nano X.
This website discusses the process, but it should be possible using Ledger Live now. Dash does not have a maintained electrum wallet. Use the internet and search on the process.
Signing Messages with Ledger Nano S / Nano X - Ledger Live, Electrum
Wondering how to sign a message with your Bitcoin and Ethereum address using Ledger Nano S & Nano X? Learn to sign a message with Ledger wallet.
coinguides.org
Hi! The first thing I want to say is thank you for your work!
Question 1:
You probably made a mistake. No version Ubuntu 21 LTS. Maybe Ubuntu 20 LTS?
Question 2:
Do I need to make settings for the server from your previous manuals before starting DMZ?
Hi! Yes, I made a mistake, I meant Ubuntu 20 LTS, not 21. The sentinel will be updated to work with 22, but until then, it is safer to use previous version.
Nope, just start fresh with the DMZ. If you did follow the guide already and want use DMZ now to update the masternode and manage it, that will work too, they are compatible with each other, but I think starting from fresh is better because the DMZ will apply some tweaks to the system to make it work better with Dash Masternode and it only does this once when it first runs, after that, it doesn't re-apply them.