• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Dash Core v0.14 on Mainnet

Status
Not open for further replies.
Say hello to my little friend...

https://www.node40.com/hosting/

Node40-Perry-300x300.png
 
Past performance is not indicative of future results
True but with r=0.99 it's compelling. The slope is tapering slowly which means it's probably not truly linear, but asymptotic with a % of nodes banned per time period instead of a fixed number which makes more sense. This defines a masternode half-life under the DKG Spork, new stat coming soon!
 
True but with r=0.99 it's compelling. The slope is tapering slowly which means it's probably not truly linear, but asymptotic with a % of nodes banned per time period instead of a fixed number which makes more sense. This defines a masternode half-life under the DKG Spork, new stat coming soon!
The trend will revert soon: Nodes are getting updated, configurations reviewed and fixed, hardware/VMs upgraded to recommended specifications and firewall rules adjusted.
I have seen worse drops in node count during the last 5 years :)

Actually DKG works as expected: Finally a working PoSe scheme we have been looking for so long. "ProofOfPing" which was used before was a sham, there is even a sophisticated tool for faking (phantom)nodes out there: Earn masternode rewards without providing service to the network. These days are over.

Looking forward for the next stat update - thanks for taking the time to capture the data.
 
I'm glad i went overkill with my masternode specs awhile back in preparation for Dash Evolution.
Also good to hear that user error, misconfiguration or insufficient hardware resources are the main cause of PoSe banning.

Current number of active masternodes with a PoSe Penalty Score : 285 (diminishing)
Source : https://www.dashninja.pl/deterministic-masternodes.html
 
Last edited:
  • Like
Reactions: AjM
The service works great for correctly configured MNs. I contacted moocowmoo a few days ago [email protected] and he helped me.

How did you contact him? I've been trying to contact him for months, through both email and discord. I've stopped using the service but since there's no way to pay him, there's no way to stop paying either.
 
No, they are the same since Dash 12.1 - but some operators seem to run their nodes below minimum specs (1GB RAM) which is not sufficient since DKG got activated. 2GB RAM should still be on the safe side, i am hosting all my nodes on 4 GB RAM for more headroom. RAM is a commodity, you should not cut it short.

--> https://docs.dash.org/en/stable/masternodes/understanding.html#masternode-requirements

View attachment 9548
I'm using 8GB on the servers I host.
None of the hosted MNs went into penalty.
Spending a couple of bucks more at least cut you some problems out of your head.
I'd say recommended ram now is 4GB. Wait drive and other tools getting into play soon and 4GB will be the minimum
 
node with 2GB does not start too.
Start dashd with -reindex, it should help if it is blockchain/database/index corruption.
Also swapfile can help if its possible, not all VPS provider allow this.
 
Start dashd with -reindex, it should help if it is blockchain/database/index corruption.
Also swapfile can help if its possible, not all VPS provider allow this.
does not start with reindex. reboot and start with reindex helped.
 
  • Like
Reactions: AjM
Current number of active masternodes with PoSe Penalty score : 197
(from 310 to 197 in two days)
 
New documentation on troubleshooting PoSe bans is here: https://docs.dash.org/en/stable/masternodes/maintenance.html#proof-of-service-bans

@camosoul I am not a programmer and do not read code, so it seems like a red herring to claim that these are prerequisites for contributing to the docs. If you are still interested in helping out, the documentation is open source under MIT license and accepts contributions in the form of issues or pull requests (currently to the 0.14 branch) in plain English here: https://github.com/dashpay/docs

As has been said many times here, all bans can be attributed to weak hardware, user error or incorrect configuration. This must be rectified to provide proper service to the network - remember that masternodes exist to serve the network, the network does not exist to pay masternode owners simply for holding Dash. This is Proof of Service, not Proof of Stake. Masternodes will also soon be serving DAPI to the broader internet - it is critical that all masternodes in the valid set are configured correctly and participating in DKG when interacting with real world users. Providing erroneous service to users would quickly erode trust in the network as a whole.
 
Status
Not open for further replies.
Back
Top