{"id":30250,"date":"2019-06-13T00:11:24","date_gmt":"2019-06-13T00:11:24","guid":{"rendered":"https:\/\/www2019.dash.org\/?p=30250"},"modified":"2021-09-18T11:43:33","modified_gmt":"2021-09-18T11:43:33","slug":"hundreds-of-dash-masternodes-offline-as-network-tightens-performance-standards","status":"publish","type":"post","link":"https:\/\/www.dash.org\/news\/hundreds-of-dash-masternodes-offline-as-network-tightens-performance-standards\/","title":{"rendered":"Hundreds of Dash Masternodes Offline As Network Tightens Performance Standards"},"content":{"rendered":"

The Dash network has\u00a0tightened its standards<\/a>\u00a0for masternodes, resulting in hundreds of nodes going offline due to the new performance requirements.<\/p>\n

Last week, Dash\u2019s DKG (distributed key generation) spork was activated, spurring the creation of long-living masternode quorums (LLMQs) for a new way of running the Dash network, enabling innovations such as\u00a0ChainLocks<\/a>\u00a051% attack-proofing. As part of the upgrade, masternodes, in addition to simply remaining online, now have to provide consistent service benchmarks to the network, and receive a\u00a0score based on service provided<\/a>:<\/p>\n

\u201cProof of Service (PoSe) is a scoring system used to determine if a masternode is providing network services in good faith. A number of metrics are involved in the calculation, so it is not possible to game the system by causing masternodes to be PoSe banned for failing to respond to ping requests by e.g. a DDoS attack just prior to payment. Each failure to provide service results in an increase in the PoSe score relative to the maximum score, which is equal to the number of registered masternodes. If the score reaches the number of registered masternodes, a PoSe ban is enacted and the masternode must be repaired to ensure it provides reliable service and registered in the list again using a ProUpServTx. The current scoring rules as of Dash 0.14 are:<\/p>\n