Update on Network Instability
out-of-memory issue identified and mitigatedHello Crown Community,
this is an update on the issue the Crown Network has been experimenting since last night around 11 PM CEST:
Many nodes started to fail around September 29th 23:00 CEST. This failure was caused by an out-of-memory error. The development team was inmediately alerted.
After pertinent analysis by our devs, @ashot found there is a very big amount of InstantSend transactions. One of the assumptions is that the Crown Network underwent a DDoS attack. Further research is in process in order to confirm this. The generalized failure, which would crash nodes also after restart due to an out-of-memory error, led to a split block, so that the network could not agree anymore. The block that was causing the dissensus has been identified and InstantSend has been deactivated. All transactions are currently processed in a standard way.
A full analysis report will be published once the research on this issue has been completed.
Please refrain from depositing to exchanges before their “block updated” matches
https://chainz.cryptoid.info/crw/Instructions to get nodes back online:
Local wallet:
Backup wallet.dat
Check that block height matches
https://chainz.cryptoid.info/crw/if it does not match, go to Tools > Repair Wallet > Rebuild Index (-reindex)
Check blockheight
Remote wallet:
crownd
wait for sync
crown-cli getinfo
check block height matches
https://chainz.cryptoid.info/crw/if it matches, go to step 10. If not, continue with step 6.
crown-cli stop
crownd -reindex
wait for sync
check block height matches
https://chainz.cryptoid.info/crw/start nodes from local wallet
check status with crown-cli systemnode status or crown-cli masternode status
If you need any further assistance, please contact us through Mattermost, Discord,Telegram, or
support@crown.techhttps://mm.crownlab.euhttps://discordapp.com/invite/rB3Kr86https://t.me/crownplatformThank you for your patience and understanding!
The Crown Core Team
https://medium.com/crownplatform/update-on-network-instability-5ebf721e2e77