UPDATE. We've identified and isolated the issue leading to the network split.

17 Feb 2024, 16:39

UPDATE We've identified and isolated the issue leading to the network split. The issue stemmed from our initial setup of the cluster with single-core nodes, contrary to the recommended dual-core configurations. This limitation prevented the nodes from parallelizing the network and consensus processes effectively. As a result, nodes experienced intermittent detachments from the network and a situation of eclipses. The situation was further complicated by the extremely fast block time's impact on our finality parameter configuration, leading to one network partition erroneously considering a lower priority block as final. In response to these findings, our team is actively developing a patch to rectify these issues. We are committed to work on this patch over the weekend. To ensure that our community members are not adversely affected by these challenges, we have decided to pause the grace period, safeguarding your rewards during this period of adjustment. Additionally, our new Discord-based faucet is on track to be released and available already this evening. The active participation of the community is already bearing fruits by bringing technical issues such as those detected to the surface, and giving us the possibility to work towards a more robust and resilient network.