Evonode quick start guide

Dear Xkcd and Qwizzie,

Thanks a million for all the support. I will be trying out your suggestions and report back. The support I am getting from you guys is amazing. Very grateful.
 
Hi guys,

I followed Qwizzie'a advice. Unfortunately no change. DET immediately crashes / shuts down after entering the protx and the private key. Doesnt matter if it is the key for voting, owner or payout.
Also I am on the latest version of DET and Dash Core.
I did manage to chek the error log file (det.log). Says the following:
------
2025-02-19T15:40:40.868318Z WARN request routine: rs_dapi_client::dapi_client: retrying error with sleeping 0.01 secs error=ExecutionError { inner: Transport(Grpc(Status { code: Unavailable, message: "invalid peer certificate: Expired", source: Some(tonic::transport::Error(Transport, ConnectError(Custom { kind: InvalidData, error: InvalidCertificate(Expired) }))) })), retries: 0, address: Some(Address { ban_count: 0, banned_until: None, uri: https://37.60.236.201:443/ }) }
------
I am on ubuntu by the way.
 
Bitterender said:
Hi guys,

I followed Qwizzie'a advice. Unfortunately no change. DET immediately crashes / shuts down after entering the protx and the private key. Doesnt matter if it is the key for voting, owner or payout.
Also I am on the latest version of DET and Dash Core.
I did manage to chek the error log file (det.log). Says the following:
------
2025-02-19T15:40:40.868318Z WARN request routine: rs_dapi_client::dapi_client: retrying error with sleeping 0.01 secs error=ExecutionError { inner: Transport(Grpc(Status { code: Unavailable, message: "invalid peer certificate: Expired", source: Some(tonic::transport::Error(Transport, ConnectError(Custom { kind: InvalidData, error: InvalidCertificate(Expired) }))) })), retries: 0, address: Some(Address { ban_count: 0, banned_until: None, uri: https://37.60.236.201:443/ }) }
------
I am on ubuntu by the way.
Click to expand...

I would find that peer with this IP address https://37.60.236.201:443/ in the DET conf or env files and delete it. It is a peer which is incorrectly configured at the moment. It is possible the DET does not handle this case correctly and a bug should be reported in case someone else can reproduce the same effect.
 
xkcd said:
I would find that peer with this IP address https://37.60.236.201:443/ in the DET conf or env files and delete it. It is a peer which is incorrectly configured at the moment. It is possible the DET does not handle this case correctly and a bug should be reported in case someone else can reproduce the same effect.
Click to expand...
Removed it and tried again. Now it just mentions another ip address in the list. Removed that also. No change. Just shuts down after entering the protx and the private key. any suggestions are welcome.
 
Bitterender said:
Removed it and tried again. Now it just mentions another ip address in the list. Removed that also. No change. Just shuts down after entering the protx and the private key. any suggestions are welcome.
Click to expand...

I would check the next node that is appearing in your logs and see if that one has a problem too, if so, I would remove it too. You can verify the node is working by trying to load it in your browser. In case it says method not found, it is working, in case the browser complains about an insecure website, it is not working. Alternatively, you can search the IP on this page https://mnowatch.org/evonodes/ and ensure it is at the correct height and has two check marks.
 
Bitterender said:
Removed it and tried again. Now it just mentions another ip address in the list. Removed that also. No change. Just shuts down after entering the protx and the private key. any suggestions are welcome.
Click to expand...
Do you have a Windows pc (use DET advanced settings under Networks to set a custom Dash-QT path and overwrite the dash.conf) or a MAC pc you can install Dash Core and DET on and see if loading your Evonode identity works there ? There will always be some bad connections, but that should not give the issue that you are seeing (Evonode identity not loading / DET crashing).

Maybe best at this point to report your issue here : https://github.com/dashpay/dash-evo-tool/issues and perhaps also on Discord.
Give information there about your cpu (command lscpu) and Ubuntu version. I assume you are using Ubuntu Desktop, not Ubuntu server.
Both DET and Dash Core need to run in a full (not virtualized) desktop environment.
 
Last edited:
xkcd said:
I would check the next node that is appearing in your logs and see if that one has a problem too, if so, I would remove it too. You can verify the node is working by trying to load it in your browser. In case it says method not found, it is working, in case the browser complains about an insecure website, it is not working. Alternatively, you can search the IP on this page https://mnowatch.org/evonodes/ and ensure it is at the correct height and has two check marks.
Click to expand...
Dear Qwizzie,
Tried it. Says: "Method Not Allowed" upon trying the supposedly incorrectly configured "https://37.60.236.201/".
 
qwizzie said:
Do you have a Windows pc (use DET advanced settings under Networks to set a custom Dash-QT path and overwrite the dash.conf) or a MAC pc you can install Dash Core and DET on and see if loading your Evonode identity works there ? There will always be some bad connections, but that should not give the issue that you are seeing (Evonode identity not loading / DET crashing).

Maybe best at this point to report your issue here : https://github.com/dashpay/dash-evo-tool/issues and perhaps also on Discord.
Give information there about your cpu (command lscpu) and Ubuntu version. I assume you are using Ubuntu Desktop, not Ubuntu server.
Both DET and Dash Core need to run in a full (not virtualized) desktop environment.
Click to expand...
Yes I am in a desktop environment. Unfortunately I only have Ubuntu (linux) pc's at my disposal.
 
Bitterender said:
Is there a way to access the credits on a Evo masternode without using DET? Or is DET the only way?
Click to expand...

It is the only way, in case you trust me, you can send me your owner private key and I will do the withdrawal for you. Note that it will be impossible for me to steal from you since the funds can ONLY go to YOUR payout address. DM me your owner private key and I will do it for you. Alternatively, try the DET on a different machine, this is easier said than done, because you will also need a fully synced Dash Core, but it might be your only option.
 
xkcd said:
It is the only way, in case you trust me, you can send me your owner private key and I will do the withdrawal for you. Note that it will be impossible for me to steal from you since the funds can ONLY go to YOUR payout address. DM me your owner private key and I will do it for you. Alternatively, try the DET on a different machine, this is easier said than done, because you will also need a fully synced Dash Core, but it might be your only option.
Click to expand...
I trust you 100%. The thing is, I am not badly in need of those credits at the moment. I just want to make myself knowledgeable on the basics of operating the node. To me, that is most important. I will keep soldiering on until I get it right. Patience is a virtue and I will not give up on Dash. Thanks though for offering your kind help. I will let you know how things are going.
 
Last edited:
Dear all,
Success! I removed the previous DET installation and followed the installation instructions on github.com/dashpay/dash-evo-tool/. This was successful. Everything went smooth and identity could be loaded this time. Guys, I cannot thank you enough. The Dash community is great and always willing to help. Thanks again!
 
Bitterender said:
Dear all,
Success! I removed the previous DET installation and followed the installation instructions on github.com/dashpay/dash-evo-tool/. This was successful. Everything went smooth and identity could be loaded this time. Guys, I cannot thank you enough. The Dash community is great and always willing to help. Thanks again!
Click to expand...

That's wonderful news! I am glad you finally got it working ! and the system just paid out again, great timing!

Evonodes

Dash Evonodes information
mnowatch.org
 
A question: I have had a couple of payouts from my Evo node. The amount of Dash of these payouts varies wildly. One time the payout is around 9 Dash, the other time it is only 5. Masternode is stable and chugging along nicely. What is the reason for these variations in the payout amount?
 
Bitterender said:
A question: I have had a couple of payouts from my Evo node. The amount of Dash of these payouts varies wildly. One time the payout is around 9 Dash, the other time it is only 5. Masternode is stable and chugging along nicely. What is the reason for these variations in the payout amount?
Click to expand...


There is a random element to being selected to partake in quorums, this is the reason for erratic eMN payments, over several cycles it averages out to the stated APY.

To best increase your chances of block proposal, make sure you VPS is running fast enough to keep up with the load and make sure the time on your VPS is accurate to the second.
 
Bitterender said:
A question: I have had a couple of payouts from my Evo node. The amount of Dash of these payouts varies wildly. One time the payout is around 9 Dash, the other time it is only 5. Masternode is stable and chugging along nicely. What is the reason for these variations in the payout amount?
Click to expand...
This is currently my estimate with regards to APY for Evonodes :

Knipsel.JPG


So currently i personally estimate an Evonode should get about 0.845 trillion credits / 8.4 dash per epoch (9.125 days).

Since the Platform chain has a Gaussian distribution system (see below pics), Evonodes can get below that estimated number, above that estimated number or more or less reach that estimated number. During this last epoch both my Evonodes were below my own estimate of 8.4 dash (5.80 dash & 8.13 dash), with the main difference between my Evonodes : having 4 proposed blocks more then the other.

download1.jpg
download.jpg


Hopefully we get above that estimate with the next epoch. If an Evonode is consistently getting below estimated number, then there could be a problem with the Evonode itself. But on the other hand i am not sure how many epochs it will actually take to get from operating far of the mean to operating near the mean. Maybe it could take a few epochs, maybe it could take many epochs.

A better approach would be to use a deterministic distribution system, like how Masternodes and Evonodes get their rewards from L1.
This Gaussian distribution system (and its heavily unpredictable element) on L2 can get on people's nerves. Specially when their Evonode is operating far from the mean and therefore receive less rewards from L2.
 
Last edited:
You must log in or register to reply here.
Back
Top