Zilliqa block production ‘interrupted’ by critical technical snag


Zilliqa block production ‘interrupted’ by critical technical snag



On Dec. 18, the Zilliqa core team announced a critical technical issue affecting block production in their network.

The team announced the development on social media and said that it is investigating the issue as a top priority. It added that the technical team is already working on identifying and resolving the problem.

Network issues

The network outage has led to an interruption in the blockchain’s normal operations, prompting the Zilliqa team to advise all partners and users to temporarily stop any deposits or withdrawals on the network to avoid complications.

This precautionary measure is essential to maintain network integrity and safeguard user transactions during the outage.

Acknowledging the inconvenience caused by the disruption, the Zilliqa Core Team expressed their gratitude towards the community for its patience and support. They emphasized the importance of community understanding as they navigate through the challenge.

Verifying funds

In a bid to assure users about the safety of their funds, the team emphasized that all funds are secure. To alleviate concerns about inaccessible funds in wallets, the team provided a resource for users to verify their funds on-chain.

Users can confirm the status of their funds by visiting the blockchain scanner and entering their ZIL address.

Launched in 2017, the Zilliqa blockchain employs sharding to enhance scalability, a significant challenge in blockchain technology. Sharding divides the network into segments, or ‘shards,’ for more efficient transaction processing, differing from the linear processing of traditional blockchains. This allows Zilliqa to handle increasing transactions per second as the network expands. Zilliqa also features its native cryptocurrency, ZIL, for transaction facilitation and network node rewards.

As the situation unfolds, the Zilliqa Core Team assured its community of its dedication to resolving the issue and restoring normal network operations as soon as possible.





Source link