Ethereum progress: beacon chain, Altair upgrade, merger, pledge, etc.

Beacon chain

ConsenSys researchers Joanne Fuller and Franck Cassez completed the verification of the beacon chain specification in the Dafny language, laying the foundation for future protocol development and analysis. You can go to the document link to learn more and run the certificate yourself.


Translator’s Note: Dafny is a programming language introduced by Microsoft for program correctness verification.

In addition, the Eth2 API specification has been updated to v2.0.0 to prepare for Altair’s upgrade.

One of the goals of Altair’s upgrade is to allow light clients to run efficiently on the Eth2 network so that users can run light clients trustlessly through a browser, instead of sending transactions through Infura or other trusted third parties. You can check the article “Starting the Beacon Chain Light Client Ecosystem” written by Alex Stokes to learn more.

An interesting fact: The Eth2 deposit contract has surpassed the wrapped Ether (w ETH ) contract, becoming the contract with the most ETH holdings.

Ethereum progress: beacon chain, Altair upgrade, merger, pledge, etc.

Data source:

Altair upgrade

The start time of the beacon chain Altair upgrade on the testnet Pyrmont has been determined to be epoch 61,650 and slot 1,972,800, which is 12 noon UTC on August 19 (plus 7 seconds).


EIP-3675 is a specification that merges the Eth1 execution layer and the Eth2 consensus layer. ConsenSys researcher Mikhail Kalinin explained EIP-3675 in detail in the PeepAnEIP series of Ethereum Cat Herder.

Square Ethernet client Nethermind from Eth1 point of view, published its views on the EIP-3675 is on Twitter.


On August 11th, StakeHouse held the 5th community meeting. If you want to know the progress of the GUI client installer and other projects, you can enter the document link to view.


In order to achieve client diversity, Colfax from EthStaker and StakeHouse made some great suggestions. I would love to see these points listed by Colfax can be realized one by one.

  • Good data and user education
  • Client UI
  • Add the client to DappNode and AvadoCloud
  • Build a multi-client UI
  • Standardized key management
  • Client switching tool
  • Build client package software through PRA

Regarding client switching, I personally can accept the solution of homogenizing the client to facilitate switching, but this will make the product manager a little frustrated. I think another solution can be considered-making the client “different”. That is, each client is optimized for specific user groups and use cases. Nimbus focuses on low-power devices, while Teku focuses on the institutional pledge market, which may also promote client diversity.

We can also try to do a two-pronged approach, using both methods.


  • has optimized the validator monitoring App. You can import your node data into the App through the client data export tool. Lighthouse does not need this tool to import node data, and the Teku team is also investigating the native support for data import functions.

Decentralized pledge

On August 11th, SSV held the second community meeting. BloxStaking CEO Alon Muroch demonstrated the launch of the SSV public testnet. (SSV refers to the Secret Shared Validator. I personally think it is more appropriate to call it Distributed Validator or Resilient Validator.)

At the same time, the Rocket Pool testnet has entered Phase 4-simulating a completely open Rocket Pool.

Good article recommendation


Currently, blocks on the beacon chain require two epochs (about 13 minutes) to achieve finality. The deterministic delay means that the verifier has the opportunity to reorganize the newly generated block through time robber attacks and other methods, posing a threat to the stability of the beacon chain.

When the cost of reorganizing the chain after a slot is high, the new block may be able to achieve a certain degree of economic finality. Ethereum founder Vitalik proposed such a mechanism in his article “Committe-based Cumulative Finality Model”. It will be another way for Ethereum to implement the Casper CBC consensus in the future. It will also lower the threshold for the amount of Eth2 pledge and allow more users to enter the Eth2 network to become validators.

The idea of ​​separating the roles of the shard block builder and the shard block proposer has become more grounded. The early design has been incorporated into the sharding specification, and its main goal is to eliminate the information asymmetry of MEV and democratize MEV so that its value is not only captured by large staking pools.


Posted by:CoinYuppie,Reprinted with attribution to:
Coinyuppie is an open information publishing platform, all information provided is not related to the views and positions of coinyuppie, and does not constitute any investment and financial advice. Users are expected to carefully screen and prevent risks.

Like (0)
Donate Buy me a coffee Buy me a coffee
Previous 2021-08-19 11:41
Next 2021-08-19 11:44

Related articles