According to Trustnodes March 7 news, Nishant Das, an Ethereum 2.0 client developer from Prysmatic Labs, said recently that the Prysmatic client developed by his studio can already "interact" with the Lighthouse client, he said:
"Finally connected to the Lighthouse client … synchronized some blocks from the Lighthouse node."
- ETF's annual developer conference Devcon four highlights
- Ethereum Foundation: Ethereum Studio is officially launched, the development environment is simple and easy to operate
- Twitter Featured: Ethereum 4th Anniversary, From ICO to DeFi, Breaking From Death Spiral
- Vitalik: Quick Start on Garbled Circuits
- Vitalik's latest speech: 51% of nested attacks become a deadly threat to PoW blockchain, PoS is the only way out
- Vitalik: A new way to implement cross-segment trading
Image source: Pixabay
For several months, he has been trying to make this node "conversation" with another Ethereum 2.0 client Lighthouse. His work has started since November last year, and has recently stepped up efforts in early February this year.
As Terence Tsao, another Prysm developer, described, developers have now achieved the goal of "one step closer to multi-client testnets". This particular Lighthouse testnet was released at the ETHDenver conference, and more to allow developers to test each other. Lighthouse's Manning says:
"This test network has no certified subnets or aggregate topics, so if Prysm expects synchronization, you may run into problems."
As you may know, a subnet is a shard. But Topic is still a new term for us. It looks more like how to send transactions to different shards. Manning revealed that a new interoperability testnet is coming online, and he said:
"We are completing some edge tests, doing some local tests, and then launching an 'interoperability' testnet that has all the features including denoising and data compression."
When will it launch? Although the estimated time may be meaningless, this is a good question. The developer has now reached the stage of centralizing the optimization of the user interface (UI). We were told that the storage contract is expected to be ready by April, and Ethereum 2.0 coordinator Danny Ryan seems to be working on a new specification.
The beacon chain specification has been audited and some changes have been made as a result, so the new specification version 0.11 is a key step in launching a multi-client testnet. At this time it is still basically running with virtual funds under laboratory conditions instead of using real ETH.
Single-client testnets have been running for several weeks, and they are tweaking and improving some edge instances. One of them is that if Ethereum 1.0 is upgraded to include BLS signatures, it will be more secure.
Ethereum 1.0 developers have stated that this upgrade may take place in June, so if the multi-customer testnet can run normally for 3 months next month, they may reach the Ethereum 2.0 genesis block on July 30. The target that was dug out a few days ago.
However, because it is difficult to evaluate the work that must be done and the work to be done, there is no set date, but many Ethereum 2.0 client development teams have added new developers, so the development work has been methodical. get on.
This means that the basic framework of staking and sharding has now taken shape. Once the multi-client testnet is launched, Ethereum 2.0 will become very specific, because then we can all use it to view the new chain of these subnets. What is it.