A couple of the statistics we monitor are the total number of active Dash masternodes and the number of masternodes that are pose_banned. As we write this, over five percent of masternodes are POSE_BANNED. If your masternode falls into that category, we should talk!

Proof of Service Explained

The Dash network relies on masternodes to process transactions. To determine if masternodes are up to the task, Dash uses a proof-of-service metric, which is constantly monitored. Per the Dash documentation:

The Proof of Service (PoSe) scoring system helps incentivize masternodes to provide network services. Masternodes that neglect to participate receive an increased PoSe score which eventually results in them being excluded from masternode payment eligibility.

Failure to Prove…

If you run a masternode, perhaps you have experienced a status of POSE_BANNED. The scoring system ensures that each node is carrying its weight, and if it isn’t, it’s removed from the processing queue. Issues must be addressed and the node re-added to the queue to resume processing. As a managed service provider (we host masternodes), we employ “self-healing servers” that will solve many issues without our intervention. We’ve had occasions, though, where we had to intervene. Problems like failing hardware and underpowered servers (inadequate disk space or memory) can occur. For example, if you set up a server a few years ago, the Dash blockchain has grown, increasing the load on processing power, disk drives, and memory. Your older machinery may not perform well enough anymore. That’s why you may be POSE_BANNED.

Dash Is Evolving…

If you’ve been paying attention to Dash news, the initial version of Dash Platform (FKA Evolution) is nearing completion. Recent “maintenance” releases have been gearing up for the next major release. And guess what? It needs more processing power. Prepare to evolve.

As an example of upping the performance ante, Dash Platform will have High-Powered Masternodes (HPMN) that will require a higher stake and much higher system specifications — the idea is for them to do more work and earn higher rewards. dApps, the key reason for Dash Platform, need significant data storage. Dash Core Group described them:

A High Performance Masternode is a proposed new type of Masternode which would be used to serve the network by participating in consensus on both the Dash Platform chain and the Dash Payment (Core) chain. In the solutions that use HPMNs the standard Masternode would continue serving only the Dash Payment chain. HPMNs would have greater requirements than a standard Masternode regarding collateral amount and would require higher performance specs as they would be running two chains instead of just one.

POSE_BANNED Masternodes

Keeping your masternode running smoothly is imperative to earn rewards. We like to say “Just Say NO to POSE_BANNED“. We do our best to manage that! As Dash evolves, you’ll need to monitor more closely, at least until the digital dust settles…