Welcome to this week’s eth2 quick update! A handful of new eth2 testnets have come online and last week I had them all running on my laptop. There is still plenty of work to be done, but this is getting real :).

tldr;

Comprehensive Phase 0 audit to be conducted by Least Authority

We are excited to announce an upcoming eth2 spec audit to be conducted by Least Authority. This is a comprehensive security audit of the eth2 core Phase 0 specifications focusing on critical items such as Denial of Service (DoS) attacks, resource misuse attacks that could lead to unintended forks/adversarial chains, network related attacks, any attacks that impact funds, and more.

Least Authority is a leading expert in mechanism & incentive design, decentralized/distributed systems architecture, and analysis of blockchain systems. The Ethereum Foundation has previously engaged with Least Authority on work in the past such as an audit of discv5 and an analysis of gas economics and proof of work, and we are excited for this opportunity to work with them again. A comprehensive security audit as critical to a successful launch of Phase 0, and we eagerly await the initial report to be released in early February.

Lighthouse launches testnet with mainnet configuration

Last week, Sigma Prime launched their long-awaited public Lighthouse testnet. This testnet impressively ran the mainnet spec configuration, and at its peak was easily handling 16815 active validators!

As stated by Sigma Prime at the launch of this net, “we’re going to start trying to crash this testnet and I suspect we’ll be successful”, and successful they were. After recovering from non-finality of 100+ epochs due to two of their validator-heavy nodes going offline, the Sigma Prime team decided to take down the network to iron out some bugs, work in some new optimizations, and restart fresh soon. Check out the postmortem here. As discussed on today’s eth2 call, the team intends to relaunch the testnet tomorrow, opening it up for public use after initial stability testing.

Remember to be an active participant in these early testnets if you feel capable: If something isn’t clear in the docs, let them know. If you have trouble compiling, open an issue. If there’s a typo in the readme, fix it! This goes for all of the clients and for open source software in general. The more you actively give back in this process, the better things will be for everyone.

P.S. Sigma Prime is hiring a full-time experienced Rust developer to work on Lighthouse. Check it out!

Nimbus integrates native nim-libp2p

Earlier this year, the Ethereum Foundation, Protocol Labs, and Status co-funded a grant for Nimbus to create a native Nim language implementation of libp2p. This implementation was to be integrated into the nimbus eth2 client as well as to become a p2p networking option for resource restricted devices.

We are pleased to announce that Nimbus just recently integrated this native implementation into their codebase and plan on restarting their testnet with it this coming week. This is a huge milestone both for Nimbus and also for the p2p community at large due to Nim’s ability to compile succinct and efficient code for most computer architectures. The Nimbus team continues to kill it – they are truly a powerhouse of enginering! P2P all the things!

beaconcha.in adds support for Lighthouse

Bitfly’s open source eth2 block explorer, beaconcha.in, just added support for Lighthouse! You can give it a look here, but things are currently inactive until Lighthouse reboots their network.

We are super excited to see multiple client implementations being onboarded, aiding in creating common interfaces for external software to query and understand the internals of eth2. This and other tools will be crucial in monitoring, understanding, and interacting with upcoming testnets and eventually mainnet!

Eth2 spec release schedule

We released eth2 spec verson v0.9.3 – rm signing_root and have v0.9.4 with a testing fix and network update in the queue. These are the last in the v0.9.x series of minor updates since the un-freezing of Phase 0 in October. These recent spec releases have been primarily focused on ensuring the Phase 0 Beacon Chain is flexible enough to accommodate the new Phase 1 sharding design, but some clean-ups, bug fixes, enhanced testing, and networking updates have also made it into the changelog. Many of these changes have been informed and driven by the continued client progress on testnets and general readying for mainnet.