Soon after the launch of the dress rehearsal for Ethereum 2.0 Genesis, Spadina, it faced some problems.
Later, when the developer spearheading the testnet efforts, Danny Ryan, came to know about this problem. He stated that now the team will design a new dress rehearsal for the upcoming proof-of-stake, Ethereum 2.0.
Spadina For Creation Of First Block
The short-term testnet allows the developers to create the first block on Ethereum 2.0.
It is to be noted that Ethereum, which is the second-largest network in the world, is trying to shift its position from proof-of-work to proof-of-stake.
As the network successfully moves towards the proof-of-stake position, it will experience the blockchain is less-congested and also has lower gas fees.
Notably, Spadina is not the part of Medalla, the ongoing testnet for Ethereum, they both are different. The up-and-running version of the PoS network is represented by the Medalla testnet.
However, the Spadina testnet imitates the new network’s beginning.
The blockchain created by Spadina, later, is captured by the PoS chain for up-and-running, but before the blockchain reaches the chain, it is important to test that creation.
It has been suggested that the network is being operated by at least 16,384 validator nodes and those nodes might have deposited half a million of ETH.
Spadina Is Useful
The newly launched testnet has recently highlighted some of the areas in ETH which needed improvement. This proves that the testnet is very useful.
As per the reports, compared to the blockchain, testnets are not much used by anyone because it does not have the utility which could help the non-developers.
Regarding this Ryan said, “Small errors in the client release process [greatly] exacerbated this problem, resulting in ~1/3 participation in the first few epochs.”
The Prysm Labs has recently stated that if the blockchain does not start properly, the individual should not worry about it.
It further stated that the final version of the issue does not include any critical bug nor any consensus error, but it had some configurational error, which could be fixed with the release.