[Update on Temporary outage of Bluzelle Nodes in the past few days]
Dear community, as some of you have noticed, there was a temporary outage of the Bluzelle nodes on the soft mainnet in the past few days. To provide more transparency to our loyal community and address some of the concerns, we would like to provide an update as follow:
- The Bluzelle nodes were run on Ubuntu. The issue was due to a recent auto-update of Ubuntu which resulted in a temporary shut down of the Bluzelle nodes which were holding critical power. This is NOT a bug from our network architecture or design.
- We have since restarted all nodes (with the exception of one that we have left down for investigative value).
- We have implemented further measures to ensure that nodes operating on Ubuntu will automatically restart if they ever shut down. The new measure has already been tested thoroughly and qualified as the right resolution so that our nodes have the resilience necessary to keep running and this issue won’t happen again.
- During the temporary down time, other nodes run by our community members were not affected. And due to enough decentralization, our community members had enough power to keep our soft mainnet running. This is an excellent outcome, despite the problem we faced, and shows how vital it is to have our community validators onboard.
- Two of the Bluzelle validators were jailed and slashed therefore those who delegated to these two validators were also slashed. However, we intentionally set the slashing amount extremely low for soft mainnet so the impact to these delegators are minimal. No tokens were unbonded. Other than these, all other staked tokens are SAFE.
- This experience are all part of the process of developing a new cutting-edge tech. Thanks our community for all the patience and help in stress-testing and upholding our network