A quick overview of the progress of the seven major clients of Eth2.0

Original title: a quick overview of Eth2.0's 7 Biggest Clients

Author: Somer Esat

Unitimes_Charles Unitimes_Charles

The Ethereum 2.0 upgrade is expected to be released later this year, initially with phase 0. Phase 0 includes the on-line beacon chain, which manages the PoS protocol. To interact with the beacon chain, you need a client that implements the Ethereum 2.0 specification.

In this article, the author provides a brief overview of seven Ethereum 2.0 clients currently under active development, providing information about the sources of each client, including links for readers to learn more about.

Why do you need so many clients?

You may be wondering, why are there so many clients? Why not focus on building a great "super client" once and for all?

Well, there are many reasons why having multiple clients is a good thing. Here are the two reasons I think stand out the most:

Having multiple clients means that independent developers are in a friendly competition, motivating each other with different solutions and features. Competition drives innovation.
Having more than one client means robustness, offering more options when one client fails. For example, suppose we only have one "super client". What if there is a bug or bug in this client? This could bring down the entire Eth2 network.

For these (and more) reasons, it's important to support a balanced Ethereum 2.0 multi-client ecosystem. Ethereum's core developer Danny Ryan said:

In the period leading up to [beacon chain] release, I want you to get out of your comfort zone and try different clients. There are a lot of trade-offs between these clients, and you need to use them yourself to find which one is best for you... Ethereum runs in multi-client mode, and to reap the benefits of this approach, we need users to run a variety of different clients (so that all types of clients are healthily distributed across the network).

7 big clients

Getting back to business, we're starting to dig deeper into ethereum's seven big clients. These clients are listed alphabetically by name as follows:

The Cortex (Nethermind)

Lighthouse (Sigma Prime)

Lodestar (ChainSafe Systems)

Nimbus (Status)

Prysm (Prysmatic Labs)

Teku (PegaSys)

Trinity(Ethereum Foundation)

This article will describe each client in terms of maturity, technology, functionality and support.

With the latest version of the Ethereum 2.0 specification (V0.12.1) recently released and the specification may still be undergoing changes, all clients are actively under development.

The following information is based on online sources available at the date of publication of this article.

To client teams: If there are any inaccuracies in this article, please correct them.

01. Cortex (Nethermind)

The open source Architecture client is the only.net based Ethereum 2.0 client in development. Its development company Nethermind was founded in 2017 and is located in London, UK.

While there has been no new activity in the Cortex's Github library since December, there is evidence thatThe team is developing support for Eth2.0 in the Nethermind (Eth1 client) library. At present, it is not clear whether this means that the Architecture client has been phased out in favor of the Nethermind client with more comprehensive features, or whether Nethermind will eventually become The Architecture.

Product Overview (based on Nethermind, not Architecture)

Technology: Microsoft.net Core 3.0

Platform: Linux, MacOS, Windows

License: GNU Lesser General Public License

Warehouse: GitHub. 30 contributors (submissions). The latest submission is within a few days.

Index: Prometheus

Test network: Altona test network is not yet online

The document

The Eth1 Nethermind client has a lot of documents. I couldn't find any documentation on the Eth2 Architecture client. It's probably in development right now.

The current state

Currently, it is devoted to the processing of deposit and the realization of beacon chain node.

Not Finalizing

It is worth noting that

Nethermind's Github page lists the support for the Eth2 multi-client testing network to be built in the next 6 months.

Links related Links

Web site:https://nethermind.io/

Twitter:https://twitter.com/nethermindeth

Gitter:https://gitter.im/nethermindeth/nethermind

Gitcoin:https://gitcoin.co/grants/142/nethermind

Making:https://github.com/NethermindEth/nethermind

Documents:https://nethermind.readthedocs.io/en/latest/index.html

02. Lighthouse (Sigma Prime)

Lighthouse is used by the Sigma Prime team & Lighthouse; An open source client written by Rust. Development of the client began in 2018 and the company is based in Sydney, Australia.

An overview of the product

Technology: the Rust

Platform: Linux, MacOS, Windows

License: Apache 2.0

Warehouse: GitHub. 57 contributors (commits). The latest submission is within a few days.

Index: Prometheus

Test network: Altona (Time of Creation)

The document

The Lighthouse team did a great job of providing documentation for the project. Some of the documents include:

User guide on client installation and configuration

Active Discord community

A developer blog that is updated regularly

Automatically generated source code documentation

A Contributor's guide for contributing to the project

The current state

The team is focused on implementing the V0.12.1 specification;

Participated in the launch of the latest multi-client test network Altona;

Finalizing verifier private key management;

External security audit is running;

Performance improvements in progress;

Slashing schemes are being dedicated to protect slashing validators from slashing.

It is worth noting that

Sigma Prime has an impressive "Sand on Water" interactive simulation that's fun to play and worth a try.

A link to the

Web site:https://sigmaprime.io/

Blog:https://lighthouse.sigmaprime.io/

Twitter:https://twitter.com/sigp_io

Gitter:https://gitter.im/sigp/lighthouse

Discord:https://discord.gg/cyAszAh

Making:https://github.com/sigp/lighthouse

Documents:https://lighthouse-book.sigmaprime.io/

Contributor guide:https://lighthouse-book.sigmaprime.io/contributing.html

03. Lodestar (ChainSafe Systems)

The Lodestar client is an open source client written by the ChainSafe Systems team using TypeScript. It was developed by a group of developers in Toronto, Canada. In addition to this client, the team has developed many utility packages and libraries that support Ethereum 2.0.

An overview of the product

Technology: the TypeScript

Platform: Linux, MacOS, Windows

License: GNU Lesser General Public License V3.0

Warehouse: GitHub. 30 contributors (submissions). The latest submission is within a few days.

Metric: HTTP server

Test network: Altona test network is not yet online

The document

The Loadestar team USES open communication and can read the minutes of their meetings. There are few user guides to installing the software (basically: clone, install dependencies, build, run), but the team plans to add more documentation.

Minimum user guide for client installation and configuration;

Active Discord community;

Update developer meeting notes and plans regularly;

A Contributor's guide for contributing to the project.

The current state

Applying v0.12.1 specification update and locking the online Altona multi-client test network;

The medium-term goal is to be able to reliably run a beacon node and verifier client on an appropriate test network (Altona or later) and update the documentation.

It is worth noting that

The team has implemented an education-only website, bls-Keygen.com, that allows users to generate verifier keys using Lodestar's BLS library implementation. They also have another site, Simpleserialize.com, which implements the Ethereum specification V0.11.2 consensus type and serialized values.

A link to the

Web site:https://chainsafe.io/

Twitter:https://twitter.com/chainsafeth

Discord:https://discord.gg/yjyvFRP

Making:https://github.com/ChainSafe/lodestar

Documents:https://chainsafe.github.io/lodestar/

Contributor guide:https://chainsafe.github.io/lodestar/contributing/

04. Nimbus (Status)

Nimbus is a research project and an open-source ethereum 2.0 client implementation aimed at embedded systems and personal mobile devices, including older smartphones with limited hardware resources.

The Status team has extensive experience in mobile technology with their messaging product Status. They applied their experience to building an Ethereal client that could run Archival Node and related Eth2 software on a personal mobile device.

An overview of the product

Technology: the Nim

Platform: Android, Linux, MacOS, Windows (trial)

License: Apache License 2.0 or MIT

Warehouse: GitHub. Twenty-four contributors. The latest submission is within a few days.

Metric: HTTP server

Test network: Altona (Time of creation), Onyx

The document

Provides a recently updated, concise, but to-the-point set of documentation that covers most of the information needed to get the client up and running.

User guide on client installation and configuration;

Active Discord and Status chat communities;

A developer's guide to contributing to the project.

Current state

The latest Eth2.0 specification version v0.12.1 is implemented.

Participated in the launch of the latest multi-client test network Altona;

Currently only build from source is supported;

Performance improvements and security audits are ongoing.

It is worth noting that

Nimbus is currently the only Ethereum 2.0 client for mobile platforms. Nimbus runs on the Nim language, an efficient and general-purpose system programming language with a Python-like syntax that can be compiled into C.

The team recently improved block and proof message (ATteStation) processing performance by approximately 10-50 times and client startup by 20-100 times.

A link to the

Web site:https://nimbus.team/

Blog:https://our.status.im/tag/nimbus/

Twitter:https://twitter.com/ethnimbus

Gitter:https://gitter.im/status-im/nimbus

Discord:https://t.co/CYjHgi6wFI? Amp = 1

Status:https://join.status.im/chat/public/nimbus-general

Making:https://github.com/status-im/nim-beacon-chain

Documents:https://status-im.github.io/nim-beacon-chain/

05. Prysm (Prysmatic Labs)

Pryysm client is a full-featured, well-documented open source Etheric 2.0 client developed by Prysmatic Labs (founded in January 2018).

Prysm is a mature client with a very active development team. They do a great job of interacting and supporting users of their software and test network, best known for Topaz (defunct) and Onyx.

An overview of the product

Technology: the Go

Platform: Linux, MacOS, Windows

License: GNU General Public License 3.0

Warehouse: GitHub. 48 contributors (commits). The latest submission is within a few days.

Index: Prometheus

Test network: Altona (Time of creation), Onyx

The document

Prysm has very thorough user, code and problem documentation and is well maintained. The Prysmatic Labs team has also done a great job of keeping the blog updated, which is worth reading for people who want to follow up on PrYYSM client progress.

The current state

The client has been updated to the latest V0.12.1 specification;

Participated in the launch of the latest multi-client test network Altona;

Recently conducted a security audit and is handling audit feedback;

The team is working on various optimizations;

Validator account refactoring underway.

It is worth noting that

The Prysm client has two independent binaries, one for the beacon chain and the other for the verifier. The client is also able to run a Slasher algorithm to further help secure the beacon chain and generate additional revenue.

The Prysmatic Labs team has its own stable testing network & NBSP; Onyx, where the test network is running 50,000 validators. Their previous test network, Topaz, was also in good use.

A link to the

Web site:https://prysmaticlabs.com/

Blog:https://medium.com/prysmatic-labs

Twitter:https://twitter.com/prylabs

Gitter:https://gitter.im/prysmaticlabs/

Discord:https://discord.gg/KSA7rPr

Gitcoin:https://gitcoin.co/grants/24/prysm-by-prysmatic-labs

Making:https://github.com/prysmaticlabs/prysm

Documents:https://docs.prylabs.network/docs/

Contributor guide:https://github.com/prysmaticlabs/

06. Teku (PegaSys)

The Teku client is an enterprise-class Ethereum 2.0 open source client. The client's is being built by PegaSys (a project incubated by Consensus).

Notably, The recently announced Institution-level Staking pilot project by Talsys Codefi is being built on Teku.

An overview of the product

Technology: the Java

Platform: Linux, MacOS, Windows

License: Apache License 2.0

Warehouse: GitHub. 38 contributors (commits). The latest submission is within a few days.

Index: Prometheus

Test network: Altona (startup time), Onyx

The document

Provides a recently updated, concise, but to-the-point set of documents covering most of the information needed to get the client up and running.

User guide on client installation and configuration;

A developer's guide to contributing to the project.

Current state

Has been updated to the latest specification V.0.12.1;

Participated in the launch of the latest multi-client test network Altona;

Performance optimization in progress;

Support for RocksDB metric disclosure to Prometheus has recently been increased.

It is worth noting that

Although Teku is built as an enterprise client, individual users are also free to use it.

Teku in Japanese (テ ク) is the meaning of "technology".

A link to the

Web site:https://pegasys.tech/teku/

Blog:https://pegasys.tech/blog/

Twitter:https://twitter.com/PegaSysEng

Gitter:https://gitter.im/PegaSysEng/teku

Discord:https://discord.gg/7hPv2T6

Making:https://github.com/PegaSysEng/teku

Documents:https://docs.teku.pegasys.tech/en/latest/

Contributor guide:https://github.com/PegaSysEng/teku/blob/master/CONTRIBUTING.md

07. Trinity (Ethereum Foundation)

Trinity is an open-source Ethereal client that supports Eth1.0 and Eth2.0, written by the Python team at the Ethereum Foundation. Its development began in early 2019.

An overview of the product

Technology: the Python

Platform: Linux, MacOS, Windows (not supported)

License: MIT

Warehouse: GitHub. 75 contributors (commits). The latest submission is within a few days.

Index: InfluxDB

Beta network: Altona is not online yet

The document

The team provides a reasonable set of updated documentation, including client quick start guidelines and instructions for safely running the software.

The developer of the client has a "Cookbook" document that suggests how to use the client to do some useful and interesting things, such as access to the built-in performance analysis tools.

Current state

The beacon chain specification V0.11.1 is implemented and is currently working on v0.12.1.

Working on performance issues;

Tracking metrics via InfluxDB have recently been added.

A link to the

Web site:https://trinity.ethereum.org/

Twitter:https://twitter.com/trinity_client

Gitter:https://gitter.im/ethereum/trinity

Making:https://github.com/ethereum/trinity/tree/eth2/v0.12.1

Documents:https://trinity-client.readthedocs.io/en/latest/

Contributor guide:https://trinity-client.readthedocs.io/en/latest/contributing.html

Write in the last

Now you know the seven clients! Which one do you like? I suggest you try both if possible. Once these clients can successfully target the same test network (if not Altona, then later), it will be much easier for you to run.

I'm not sure how many at least clients ethereum 2.0's main network needs to be ready to start, but it's clear that some of them are faster. How this will affect the start time of phase 0 remains to be seen.

Finally, I'd like to thank all the ethereum developers. Ethereum's ecosystem and community are filled with passionate people working toward a common goal: Ethereum 2.0. Countless developers, researchers, tinkers, and leaders are working to make it possible. Thank you all.

Text link:https://mp.weixin.qq.com

Welcome to join the official BlockBeats community:

Telegram Subscription Group: https://t.me/theblockbeats

Telegram Discussion Group: https://t.me/BlockBeats_App

Official Twitter Account: https://twitter.com/BlockBeatsAsia