Search results

https://www.dash.org/news/evo-accelerated-release/ No one had to buy more Dash, so strictly speaking, no one is asking for more money from investors. In case you are talking about proposals, to pass they always needed to reach a super majority of the votes. Were bad decisions made, yes...

These are the mysteries that we don't have good answers to at the moment because we cannot test these scenarios on testnet. What I would do in this case is set BOTH eMNs to the SAME payout address and then when you can do a withdraw for both using the one address. What the actual mechanics are...

The credits will still accumulate even if you don't have control of the address, but you would not be able to withdraw them to Dash when the time comes to do so. In the case you have the payment address on HW wallet, you would still need to produce the private key to remove the credits from...

Dear eMNOs, This is a public service announcement to let you know that you need control of your masternode payment key in order to get paid on Platform. This means in case you are currently running a evonode where the payout address is the exchange deposit address, you will be locked out of...

Dash is on the verge of finally delivering the long awaited Dash Evolution, 7 years in the making! It is interesting to see people fudding this news now at the eleventh hour. Curiously, the masternode count is not dropping, but rather increasing, the price drop has given a new cohort of...

Yes! You are right, same change there.

The code in this post https://www.dash.org/forum/index.php?threads/shell-script-to-fetch-masternodes-and-evonodes-current-voting-on-a-certain-proposal.54991/post-238678 looks perfect to me, the percentages have two decimal places of precision. The code can be shortened by removing the several...

Yeah, the variable percent_yes_emn needs what I posted above to show the correct level of precision. Here is the latest tally.

The 4x multiple is not required, unless we are adding votes to the MN votes. Some suggestions, change to Saves two lines and change, to Gives us two decimal places of precision, there is a quirk in bc that I cannot solve otherwise.

Another update to this script. I am now determining the net yes votes and then taking the percentage of those compared to all that voted, let me know if this is helpful. #!/bin/bash # Use dash-cli if working, else assume a dashmate is to be used. if dash-cli -version >/dev/null 2>&1;then...

and just for fun, I wrote this version where I removed the awk and used bash to tokenise the string on our separators, so we get each item we care about cleanly in 3 different variables. It should be faster and some systems may not have awk, so this is better. #!/bin/bash # Use dash-cli if...

Yep, you can update your original post with the new code, you are right, I missed the print out section, I did not change it. Also, the section initialising the counters is not strictly required, bash will set an uninitialised variable to zero on the first use, so you get the same results, but...

I have updated the code to make it more better. #!/bin/bash # Use dash-cli if working, else assume a dashmate is to be used. if dash-cli -version >/dev/null 2>&1;then output=$(dash-cli gobject getcurrentvotes 615d8a6d4edafdcee65ff16ab9c7bacef6f5d1b1096466c0957f0441287dcc90) else...

Thanks! This works ! 🥳

How much RAM usage are you seeing? My server is still seeing the same 11GB per instance.

This is a complete red herring. The message you are seeing is completely fine.

This will work for evonodes when we go live with them, however, the DMZ will need to be expanded to install the extra 4 or 5 services that make an Evonode tick, I will work on that when we have a stable tech stack, currently, we don't.

You can do a pull request on the site. I agree that there does seem to be deficit when dealing with the evonodes. https://docs.dash.org/en/stable/docs/user/masternodes/maintenance.html#proupservtx

Recommended approaches for this is to edit the dash.conf file located in either /etc/dash.conf or /home/dash/.dashcore/dash.conf and add the parameter reindex=1 and then comment it out after restarting.

You just did.