{"id":105394,"date":"2023-01-09T16:39:39","date_gmt":"2023-01-09T16:39:39","guid":{"rendered":"https:\/\/wp.dash.org\/?p=105394"},"modified":"2023-01-09T16:50:40","modified_gmt":"2023-01-09T16:50:40","slug":"urgent-update-to-v18-1-1","status":"publish","type":"post","link":"https:\/\/wp.dash.org\/news\/urgent-update-to-v18-1-1\/","title":{"rendered":"Urgent update to v18.1.1"},"content":{"rendered":"
Late Saturday night UTC, the Dash network experienced what appears to be an attack. The network did not go down, blocks continued to form, and there was no fork. For those who might be worried and might not understand how the system works, as a blockchain, the network can\u2019t have funds stolen (ever!) – all funds are safe.<\/strong><\/em><\/span><\/p>\n
While the attack had minimal impact on Dash users, it did affect the network infrastructure, with a great deal of masternodes becoming unresponsive. Most of the masternodes that went offline or became unresponsive were less powerful nodes that did not have enough memory to withstand the load. Thankfully, enough masternodes came back online again soon afterwards, and ChainLocks began to form again.<\/span><\/p>\n