Evonode quick start guide

[Bitterender]

You need to check the status of your free account on Zero SSL under Dashboard - Your Subscription.

If your subscriptions shows either 1-3 or 2-3 then no action is required, dashmate will auto renewal either 2 more times or 1 more time.
If it shows 3-3 then you need to create a new free account with Zero SSL, that will get you a new API key.
I create new free Zero SSL accounts through my gmailaddress, by adding gmail aliases to my main gmail address.

You will need to change some things with dashmate as well then, the whole process looks like this :

Create a new free account with Zero SSL
Obtain new API key from that new account (see developers section)

Give following commands :

dashmate config set platform.gateway.ssl.providerConfigs.zerossl.apiKey [YOUR-NEW-APIKEY]
dashmate config set platform.gateway.ssl.providerConfigs.zerossl.id null
dashmate ssl obtain
dashmate stop --safe
sudo reboot
dashmate start

Verify new cert hash that dashmate has generated with command dashmate config get platform.gateway.ssl.providerConfigs.zerossl.id and compare it with the cert hash that Zero SSL website has on their site (Certificates) by going to their cert that dashmate generated for you, pressing Copy and pasting it in notepad. The two cert hashes should match.

You can do the above 3 days before the third cert (3-3) expires. Once a free Zero SSL account is on 3-3 and the third cert has expired, you can delete that free account and use that specific emailaddress again to create a new free Zero SSL account.

What you should not do is to create certs directly on the Zero SSL website, always use dashmate and Zero SSL api key to generate the cert and then let dashmate autorenew untill it reaches 3-3.

Thanks a lot. Very helpful.

 

[tfoto]

You need to check the status of your free account on Zero SSL under Dashboard - Your Subscription.

If your subscriptions shows either 1-3 or 2-3 then no action is required, dashmate will auto renewal either 2 more times or 1 more time.
If it shows 3-3 then you need to create a new free account with Zero SSL, that will get you a new API key.
I create new free Zero SSL accounts through my gmailaddress, by adding gmail aliases to my main gmail address.

You will need to change some things with dashmate as well then, the whole process looks like this :

Create a new free account with Zero SSL
Obtain new API key from that new account (see developers section)

Give following commands :

dashmate config set platform.gateway.ssl.providerConfigs.zerossl.apiKey [YOUR-NEW-APIKEY]
dashmate config set platform.gateway.ssl.providerConfigs.zerossl.id null
dashmate ssl obtain
dashmate stop --safe
sudo reboot
dashmate start

These commands didn't work for me on my free account(

 

[qwizzie]

These commands didn't work for me on my free account(

Strange. I did this recently on a new free account and did not have any issue.
Make sure this command is without the [ ] --> dashmate config set platform.gateway.ssl.providerConfigs.zerossl.apiKey [YOUR-NEW-APIKEY]

 

[Bitterender]

Another question: once in a while I update my normal (not EVO) masternode with the latest version of the software (just did a v22.1.2 update). All is well. But how do I update my EVO node if the need arises? I understand this is a totally different process. Thanks again for your help.

 

[qwizzie]

Another question: once in a while I update my normal (not EVO) masternode with the latest version of the software (just did a v22.1.2 update). All is well. But how do I update my EVO node if the need arises? I understand this is a totally different proces. Thanks again for your help.

For Evonode operators / Masternode operators (using dashmate / Docker environment) to update to Core v 22.1.2 :

dashmate stop --safe
dashmate update
dashmate start

Check with

dashmate status
dashmate status platform
dashmate status services

This will work with small Core updates (v22.x.x), but with larger updates (v23 for example) Dashmate first needs to be updated by DCG to point to the correct major Core version.

With regards to Platform updates, xkcd usually provide the steps to update to latest Platform update (when setup through the Evonode Quick Start Guide)

 

[Bitterender]

For Evonode operators / Masternode operators (using dashmate / Docker environment) to update to Core v 22.1.2 :

dashmate stop --safe
dashmate update
dashmate start

Check with

dashmate status
dashmate status platform
dashmate status services

This will work with small Core updates (v22.x.x), but with larger updates (v23 for example) Dashmate first needs to be updated by DCG to point to the correct major Core version.

With regards to Platform updates, xkcd usually provide the steps to update to latest Platform update (when setup through the Evonode Quick Start Guide)

Dear Qwizzie,
Thanks again for your fast reply. I have just given the command "dashmate stop --safe". It is now in the process of "wait for DKG window to pass". This is now pending for several minutes. this is normal? After 15 mins or so, I got an error message stated that there were 6 failed attempts to close DKG window. After that I gave the "dashmate update" command. After checking "dashmate status" is still states that it is on version 22.0.0. Seemingly the update went ok. Any thoughts?

 

[qwizzie]

Dear Qwizzie,
Thanks again for your fast reply. I have just given the command "dashmate stop --safe". It is now in the process of "wait for DKG window to pass". This is now pending for several minutes. this is normal? After 15 mins or so, I got an error message stated that there were 6 failed attempts to close DKG window. After that I gave the "dashmate update" command. After checking "dashmate status" is still states that it is on version 22.0.0. Semingly the update went ok. Any thoughts?

You really do need to successfully stop dashmate, during a time that it is not involved with a quorum (to avoid getting PoSe scored during the stopping of dashmate). Which is why you use dashmate stop --safe

Sometimes your Evonode is just too long involved with a quorum and it will not sucessfully stop dashmate right away (leading to your error message). I would just wait a hour and try it again. When done successful, dashmate status will show Core version 22.1.2

 

[tfoto]

when is the release of platform 2.0 expected?

 

[qwizzie]

when is the release of platform 2.0 expected?

Time stamp : 13:31 and later

I suspect we will hear more about upcoming Platform 2.0 release with next Development Update three days from now.
As i understand Platform 2.0 will not include the tokens marketplace (Platform 2.1 ?). But i do think Platform 2.0 will include the
selling of tokens directly from token project owner to users (so one-way trading basically). I don't think users can actually sell those tokens
untill the marketplace is implemented.

 

[Bitterender]

You really do need to successfully stop dashmate, during a time that it is not involved with a quorum (to avoid getting PoSe scored during the stopping of dashmate). Which is why you use dashmate stop --safe

Sometimes your Evonode is just too long involved with a quorum and it will not sucessfully stop dashmate right away (leading to your error message). I would just wait a hour and try it again. When done successful, dashmate status will show Core version 22.1.2

Dear Qwizzie, after a couple tries, it worked flawlessly. MN now updated to the latest version. Thanks again!

 

[Bitterender]

Something amiss with platform explorer? It is flatlining on 'proposed blocks'. Maybe a temporary thing?

 

[qwizzie]

Something amiss with platform explorer? It is flatlining on 'proposed blocks'. Maybe a temporary thing?

Both the API and on the Platform Explorer website the implemented logic seems to only fetch from current day and only fetches incremental 5 minutes stored data / a few hours of the current day :

From my Google Sheets script with regards to epoch 19 :

Actual output :

@pshenmic

The Platform Explorer API doesn’t serve full historic day-long data anymore, only the most recent few hours of the current day.
Same for the Platform Explorer Validator site, it keeps showing 0 on the graph of proposed blocks because (assumption) it only looks at the current day and only takes into account the recent few hours of the current day.

 

[Bitterender]

Both the API and on the Platform Explorer website the implemented logic seems to only fetch from current day and only fetches incremental 5 minutes stored data / a few hours of the current day :

From my Google Sheets script with regards to epoch 19 :

View attachment 12968

Actual output :
View attachment 12967

@pshenmic

The Platform Explorer API doesn’t serve full historic day-long data anymore, only the most recent few hours of the current day.
Same for the Platform Explorer Validator site, it keeps showing 0 on the graph of proposed blocks because it only looks at the current day
and only takes into account the recent few hours of the current day.

Thank you for looking into this. Hopefully this will be resolved.

 

[tfoto]

rm -fr ~/dashmate ;wget https://github.com/dashpay/platform....0/dashmate-v2.0.0-bcbbad130-linux-x64.tar.gz &&tar xf dashmate-v2.0.0-bcbbad130-linux-x64.tar.gz &&dashmate/bin/dashmate stop --force &&dashmate/bin/dashmate update &&dashmate/bin/dashmate start &&dashmate/bin/dashmate status

 

[xkcd]

Platform 2.0.0 upgrade instructions, copy/pasta below.

rm -fr ~/dashmate ;wget https://github.com/dashpay/platform/releases/download/v2.0.0/dashmate-v2.0.0-bcbbad130-linux-x64.tar.gz &&tar xf dashmate-v2.0.0-bcbbad130-linux-x64.tar.gz &&dashmate/bin/dashmate stop --platform &&dashmate/bin/dashmate update &&dashmate/bin/dashmate start --platform  &&dashmate/bin/dashmate status

 

[xkcd]

Emergency upgrade for Platform!

Platform 2.0.1 upgrade instructions, copy/pasta below.

rm -fr ~/dashmate ;wget https://github.com/dashpay/platform/releases/download/v2.0.1/dashmate-v2.0.1-5f93c7072-linux-x64.tar.gz &&tar xf dashmate-v2.0.1-5f93c7072-linux-x64.tar.gz &&dashmate/bin/dashmate stop --platform &&dashmate/bin/dashmate update &&dashmate/bin/dashmate start --platform  &&dashmate/bin/dashmate status

 

[tfoto]

Strange. I did this recently on a new free account and did not have any issue.
Make sure this command is without the [ ] --> dashmate config set platform.gateway.ssl.providerConfigs.zerossl.apiKey [YOUR-NEW-APIKEY]

root@ubuntu-22:~# dashmate ssl obtain
❯ Obtain ZeroSSL certificate
✔ Check if certificate already exists and not expiring soon
✔ Generate a keypair
✔ Generate certificate request
✖ ZeroSSL requires an upgrade from Free Plan to Basic Plan
◼ Set up verification server
◼ Start verification server
◼ Verify certificate IP address
◼ Download certificate file
◼ Save certificate private key file
◼ Save certificate request file
◼ Save certificate file
◼ Stop verification server

 

[tfoto]

What command should I run to make sure that everything is OK with the certificate?

 

[qwizzie]

What command should I run to make sure that everything is OK with the certificate?

In case your free account came to a conclusion after the third cert expired, did you do these steps ?

Create a new free account with Zero SSL
Obtain new API key from that new account (see developers section)

Give following commands :

dashmate config set platform.gateway.ssl.providerConfigs.zerossl.apiKey [YOUR-NEW-APIKEY]
dashmate config set platform.gateway.ssl.providerConfigs.zerossl.id null
dashmate ssl obtain
dashmate stop --safe
sudo reboot
dashmate start

Verifying if cert is generated correctly by Dashmate :

Verify new cert hash that dashmate has generated with command dashmate config get platform.gateway.ssl.providerConfigs.zerossl.id and compare it with the cert hash that Zero SSL website has on their site (Certificates) by going to their cert that dashmate generated for you, pressing Copy and pasting it in notepad. The two cert hashes should match.

Also check if the HTTP port of your Evonode is green on https://mnowatch.org/evonodes/ and by further clicking on that port you get redirected to your Evonode site where you can check if it indeed has a secure connection (click on the 'View site information' button / symbol just before your ip address on top of your site). You can fetch cert info there too.

 

[tfoto]

In case your free account came to a conclusion after the third cert expired, did you do these steps ?

Create a new free account with Zero SSL
Obtain new API key from that new account (see developers section)

Give following commands :

dashmate config set platform.gateway.ssl.providerConfigs.zerossl.apiKey [YOUR-NEW-APIKEY]
dashmate config set platform.gateway.ssl.providerConfigs.zerossl.id null
dashmate ssl obtain
dashmate stop --safe
sudo reboot
dashmate start

Verifying if cert is generated correctly by Dashmate :

Verify new cert hash that dashmate has generated with command dashmate config get platform.gateway.ssl.providerConfigs.zerossl.id and compare it with the cert hash that Zero SSL website has on their site (Certificates) by going to their cert that dashmate generated for you, pressing Copy and pasting it in notepad. The two cert hashes should match.

Also check if the HTTP port of your Evonode is green on https://mnowatch.org/evonodes/ and by further clicking on that port you get redirected to your Evonode site where you can check if it indeed has a secure connection (click on the 'View site information' button / symbol just before your ip address on top of your site). You can fetch cert info there too.

I see on the site that quite a few node holders have a problem with encryption... how critical is it?