Sigma Prime's Lighthouse project has just unveiled an Ethereum 2.0 testnet that it hopes will be capable of handling 100 validators. Sigma Prime is ready to test the Ethereum 000 client before it goes live. Paul Hauner, Lead Developer at Lighthouse, posted a video revealing the ETH2.0 testnet on Twitter this week.
In a reply thread on the original video, Hauner says the testnet will run with 3.2 million “replica ETH” (or just under $800 million worth of Ether replicas). It’s another step forward for Ethereum 2.0, a complete overhaul of the second-largest cryptocurrency on the planet by market cap. The new Ethereum will solve critical problems inherent in the current implementation.
[amazon box="B078YF1H42"]Lighthouse innovating Ethereum
Mainly scalability issues that you will have to overcome before reaching mass adoption, and the «difficulty bomb». While the transition from proof-of-work (PoW) to proof-of-stake (PoS) for nodes qualified to validate transactions aims to solve both problems, the “sharding” of the blockchain database blockchain ETH2.0 PoW will address scalability. But there is a long way to go for the complex and carefully choreographed transition from Lighthouse to Ethereum.
is a client program to implement the Ethereum 2.0 specification. It is written in Rust, a programming language and syntactic cousin of C ++, with an emphasis on the safety of computer memory and concurrency. Other clients include Nimbus and Prysmatic. In a way, they are competitors, but also collaborators who need each other for the success of Ethereum. And they seem to get along. Six months after the Prysmatic testnet went live last year, the price of Ethereum had risen 50%.
Sharding to scale Ethereum 2.0
Sharding is a database scaling solution. There are two reasons why a database may need to scale. Too much load and too much data. In these cases, the database can become fragmented. Sharding is a layer one scalability solution. Describes a condition of the blockchain where the network is divided into smaller partitions. These are called chunks and contain a separate transaction history.
Once this is done, individual nodes will not have to process all transactions except for certain shards. This way, no node will have to do all the work. Sharding is especially suitable for use in blockchains, which operate on a distributed network of many nodes. However, there are also challenges. For example, queries will become much more complicated. This is why extensive stress testing is needed.
