1. Home
  2. News
  3. Ethereum news
  4. Zinken testnet to be run by Ethereum 2.0 developers after Spadina did not go smooth

Zinken testnet to be run by Ethereum 2.0 developers after Spadina did not go smooth

Photo of: Janeth Diamond
by Janeth Diamond

We earlier reported that Ethereum 2.0 is all set to conduct the dress rehearsal of the Spadina testnet, but unfortunately, the testnet which was expected to do brandishing well did not go out as planned. In order to overcome the not so successful dry run of the Spadina testnet, Ethereum 2.0 developers will run yet another testnet ‘Zinken’ in the coming few days. 

A core Ethereum developer by the name Danny Ryan mentioned that the main reason for not hitting the bull’s eye was because the testnet was subjected to long waits to block finality. It also recorded low participation from Ethereum 2.0 clients that run nodes for transaction validation. The developer categorically cited:

“Even though we expect moderately low participation on a short-lived non-incentivized testnet, small errors in the client release process great[ly] exacerbated this problem, resulting in ~1/3 participation in the first few epochs,” said Ryan. “In response to these issues, we’ll be hosting -at least- one more dress rehearsal — Zinken — prior to genesis.”

He took to Twitter to explain the deviation. 

Source: Twitter

He clearly has mentioned the reasons for a not-so-successful stint. 

As per Prysmatic Labs, one of the Ethereum 2.0 clients, the new Spadina testnet actually suffered from a lack of finality at launch due to the poor participation of Prysm nodes. This had led to utter clutter and confusion and made the Genesis rehearsal look bad. Most of the problems as reported emerged from the operational mishaps. 

Another point to note is that Prysm was not updated well to properly support Spadina. It did not have the necessary bootnode for the testnet in the alpha.26 release which was the latest Prysm release at the time of Spadina Genesis. The validator commands did not have the Spadina flag which it should have. This led to invalid deposits for anyone who tried to create a wallet with Prysm or tried to deposit with the deposit data from their created accounts. 

On top of all this, its documentation portal had just no mention of Spadina. It clearly lagged behind in terms of taking Spadina in a manner it should have in the form of having a detailed checklist ready and having a release ready before the genesis event. 

Prysmatic Labs further continued that the above-mentioned issues that have been tagged with the Spadina testnet are only deteriorating bright prospects for the Genesis rehearsal. It said that it gives a bad look for this Genesis rehearsal. What needs to be noted is that it was not due to any critical bug or consensus error that needed overhauling, but it was due to configuration parameters that are easily fixable with a release, said Prysmatic in its statement.

And now, with the Spadina testnet not going as planned, the Zinken testnet is expected to run in 10 days. Overall the impact of the Spadina testnet has been that there has been no finality in the testnet, confusion with users sending invalid deposits. This has eroded the confidence in becoming an ETH2 validator!