Evonode quick start guide

Upgrading to Platform v1.7.1 for quick start guide users is as easy as this one liner.

Code: 
rm -fr ~/dashmate ;wget https://github.com/dashpay/platform/releases/download/v1.7.1/dashmate-v1.7.1-fc7d994b8-linux-x64.tar.gz &&tar xf dashmate-v1.7.1-fc7d994b8-linux-x64.tar.gz &&dashmate/bin/dashmate stop --platform &&dashmate/bin/dashmate update &&dashmate/bin/dashmate start --platform  &&dashmate/bin/dashmate status
 
Upgrading to Platform v1.8.0 for quick start guide users is as easy as this one liner.

Code: 
rm -fr ~/dashmate ;wget https://github.com/dashpay/platform/releases/download/v1.8.0/dashmate-v1.8.0-e4e156c86-linux-x64.tar.gz &&tar xf dashmate-v1.8.0-e4e156c86-linux-x64.tar.gz &&dashmate/bin/dashmate stop --platform &&dashmate/bin/dashmate update &&dashmate/bin/dashmate start --platform  &&dashmate/bin/dashmate status
 
Dear XKCD or any other memeber who is willing to help,
I have been running a normal masternode for some time. Have no problem setting these up. I am now trying to setup an Evo node. However, I am having some trouble with this and I am very grateful for your input. If this is not the right thread to ask, please direct me to the right place. I am not a computer expert by any means, however I can follow instructions. So please have some patience.
My trouble is this: I have setup a VPN and configured it. I sent the collateral of 4k Dash to my address and followed the dashmate setup. When dashmate gives me the protx register_evo string, I put this into the dash core console. However, the console just replies with the instructions on how to use the protx register_evo command. No transaction is made (no error code either). I have gone over my input string (as generated by dashmate) many times, but I cannot discover why the command does not result in a transaction / valid return. It just keeps giving me the instruction / command explanation as I have typed in nothing. Many thanks for your guidance.
 
Bitterender said:
Dear XKCD or any other memeber who is willing to help,
I have been running a normal masternode for some time. Have no problem setting these up. I am now trying to setup an Evo node. However, I am having some trouble with this and I am very grateful for your input. If this is not the right thread to ask, please direct me to the right place. I am not a computer expert by any means, however I can follow instructions. So please have some patience.
My trouble is this: I have setup a VPN and configured it. I sent the collateral of 4k Dash to my address and followed the dashmate setup. When dashmate gives me the protx register_evo string, I put this into the dash core console. However, the console just replies with the instructions on how to use the protx register_evo command. No transaction is made (no error code either). I have gone over my input string (as generated by dashmate) many times, but I cannot discover why the command does not result in a transaction / valid return. It just keeps giving me the instruction / command explanation as I have typed in nothing. Many thanks for your guidance.
Click to expand...
You can use DMT to register your Evonode. It is more easy to register your Evonode through DMT (Dash Masternode Tool), then through manual commands in the Console of the Dash Core wallet. You can also clear PoSe bans through DMT or change payout address. For now just use a Dash Core wallet address as registered payout address for your Evonode. DMT has an issue right now with regards to handling Platform withdrawals that comes in on a Ledger wallet (Trezor One still works though).

Link : https://github.com/Bertrand256/dash-masternode-tool/tree/master

Once you registered your Evonode through DMT, you can do dashmate setup and use option 'already registered'
With Evonodes you will be required to have a Zero SSL account at https://app.zerossl.com/ (free or paid) and provide dashmate the api key of that account (you find it under 'developer'). Dashmate (through dashmate setup) will generate the zero ssl cert through that api key.
 
Last edited:
I am having trouble installing and running DMT. Am on Ubuntu. Have downloaded the zip file but am at a loss on how to proceed. Any input would be welcome. Also, I am still curious why Dashmate setup does not work for me. As stated earlier, dahsmate procides the protx register_evo command, but when i copy paste this in Dashcore console, I simply get the instructions on how to use the command on screen. No transaction and no error code. What could be causing this?
 
Bitterender said:
I am having trouble installing and running DMT. Am on Ubuntu. Have downloaded the zip file but am at a loss on how to proceed. Any input would be welcome. Also, I am still curious why Dashmate setup does not work for me. As stated earlier, dahsmate procides the protx register_evo command, but when i copy paste this in Dashcore console, I simply get the instructions on how to use the command on screen. No transaction and no error code. What could be causing this?
Click to expand...
DMT needs to run in a desktop environment. I use it in Windows 10.
When going the manual route : unlock your Dash Core wallet first, before executing the protx command in the Console. The command itself is build like this :

protx register_evo 1 2 3 4 5 6 7 8 9 10 11 12

1 : collateralHash
2 : collateralIndex (either 0 or 1 or 2)
3 : ipAndPort (ipaddress:9999)
4 : ownerAddress (address created in your Dash Core wallet and named Owner Address)
5 : operatorPubKey / BLS public key (either dashmate created it for you as BLS pair key (public and private key) or you created it in the Console of your Dash Core wallet. It needs to be written down as Dash Core will not remember this pairkey after generating it)
6 : voting address (address created in your Dash Core wallet and named Voting Address)
7 : operatorReward (0 if you are owner and want the full reward going to yourself)
8 : payout address (address created in your Dash Core wallet and named Payout Address)
9 : platformNodeID / Platform Node key (Tenderdash)
10 : 26656 (this is a fixed Platform P2P port)
11 : 443 (this is a fixed Platform HTTP port)
12 : feeSourceAddress (address created in your Dash Core wallet and named Fee Source Address)

Make sure you use all 12 fields correctly (doublecheck) and have some dash in your feeSourceAddress to pay for the protx register transaction.
If you use DMT, this will be free. If your protx register command is incorrect, it will just bring up the help screen for that command (which is what you have been seeing).

Make sure your firewall in Ubuntu allow these ports (including port 80 !!) and you disabled IPv6 :

Knipsel.JPG

Source : https://docs.dash.org/en/stable/docs/user/masternodes/server-config.html#

Knipsel1.JPG

source : https://docs.dash.org/en/stable/docs/user/masternodes/server-config.html#disable-ipv6
 
Last edited:
You must log in or register to reply here.
Back
Top