Dymension’s mainnet launch has encountered significant challenges due to consensus issues among validators.
Chorus One, the ecosystem’s largest validator, has experienced node issues that disrupted its ability to effectively participate in the consensus process. This is especially concerning because Chorus One owns 34.8% of the network’s voting rights.
In blockchain technology, validators are individuals or groups who lock tokens and run software that can store and verify data to ensure its accuracy.
Achieving consensus – a mutual agreement between validators on the validity of transactions – is critical to the functioning of the blockchain. It secures the network against fraudulent activities and ensures that only verified transactions are recorded.
Read more: The Beginner’s Guide to Consensus Mechanisms
To prevent malicious transactions, validators must agree or reach a ‘consensus’. Failure to do so may result in network shutdown.
For a network like Dymension, which aims to leverage modular blockchain architecture to provide superior performance and customization, maintaining a cohesive and stable group of validators is essential to its success and reliability.
The majority of blockchains today require 66% of the effort to agree on a topic before consensus can be reached.
However, in the case of Dymension, the failure of the largest validator meant that regardless of whether other validators had operational nodes or not, the network itself could not reach consensus.
Dymension did not respond to Blockwork’s request for comment before publication.
Chorus One noted in a post on X that all Dymension validators are currently working together to perform a restart. The team indicates that it will join the chain as soon as the problem is resolved.
“We are addressing an issue on our end that led to a less than ideal launch experience for the Dymension mainnet ~2 hours ago,” Chorus One wrote.
The team notes that the cause of the problem is still unknown, but is likely related to the network’s node software.
“We have followed all guidelines issued by [the] Dymension team, so this could be a subtle bug in the node software,” the company wrote.
It added that the reason it owned more than 33% of the network shares is that it was an early Dymension supporter who had staked a significant portion of its DYM token in the genesis block.
“Other early-stage investors had not bet on origination, leaving us with 34% of the power in the failed launch,” Chorus One wrote.
