Compiled by: Karen, Foresight News
Ethereum Foundation researcher Justin Drake proposed the final design of Ethereum at the Devcon conference today, the core of which is a large-scale redesign of Ethereum's consensus layer. He named the design and fork of this proposal "Beam". So what vision does the Beam Chain carry, and how are its technical architecture and implementation plan unfolding?
Beam Vision
Why is it necessary to redesign the consensus layer on a large scale? Justin Drake believes that the current beacon chain is outdated, with its specifications frozen five years ago, and in recent years, there have been many breakthroughs in areas such as MEV mitigation, SNARKs (Zero-Knowledge Succinct Non-Interactive Arguments of Knowledge), and zKVMs (Zero-Knowledge Virtual Machines), making the redesign of the consensus layer particularly urgent.
First, it needs to be pointed out that since the launch of the beacon chain in 2020, Ethereum has seen an important fork upgrade every year. From the increase in sync committees in 2021, to the completion of the merge in 2022, to the support for staking withdrawals in 2023, and the proto-danksharding in 2024, each step has witnessed the growth and transformation of Ethereum. In 2025, Ethereum will implement the Electra fork, including the implementation of EIP-7251 (MaxEB). In the next few years, Ethereum will also undergo some gradual forks.
However, after these gradual forks, Justin Drake believes that we may face an unprecedented challenge - the Beam fork. This is a "quantum leap" in the consensus layer, which can integrate multiple upgrades (batch) into a single fork.
It is worth mentioning that Beam is specifically targeted at the consensus layer, excluding blobs and the execution layer (including EVM), because the opportunities to modify blobs and the execution layer are quite limited, while the consensus layer is not directly used by applications, providing more opportunities for design and change.
The Beam Chain consensus layer roadmap includes three categories: block production, staking, and cryptography. In terms of block production, the introduction of inclusion lists to resist censorship, the decoupling of validators and block production processes, and ideas like execution auctions, and perhaps shortening the current 12-second slots.
In terms of staking, researchers widely believe that optimizing the current issuance curve has the potential to improve Ethereum's overall health. In addition, reducing the amount of Ether required to become a validator and achieving faster finality are also research focuses. In terms of cryptography, the main focus is on chain abstraction, quantum security, and strong randomness.
Beam Chain Technical Layer
Justin Drake believes that "after PoW and PoS, we may be entering the era of zero-knowledge proofs in Ethereum consensus. In the ZK era, SNARKs will become an indispensable technology. The entire Beam Chain, and even the entire consensus layer, can be SNARK-ized. This is the time for zKVM to shine."
It is worth noting that the parts that need to be SNARK-processed are mainly the state transition functions, which are the core of the consensus client. All the surrounding infrastructure of the state transition function, such as networking, syncing, cache optimization, or fork selection rules, do not need to be SNARK-processed. Ultimately, the state transition function is just a subset of the entire system.
Another place where Beam Chain makes extensive use of SNARKs is in aggregate signatures - using hash functions to implement post-quantum aggregatable signatures. Justin Drake explained that you can collect thousands of signatures and compress them into a proof, and by combining them, you get a hash-based post-quantum aggregatable scheme, which can also be further aggregated multiple times.
In addition, Ethereum will continue to use the existing infrastructure, including libp2p, SimpleSerialize, PySpec, and the Protocol Guild.
Beam Chain Roadmap
Justin Drake has developed a detailed plan for the launch of Beam Chain. The specification process will start in 2025, construction will begin in 2026, and testing will start in 2027 to ensure that Beam Chain meets production-grade standards and can be safely deployed to the mainnet. From the roadmap below, the mainnet deployment time may be in 2029 or after 2030.
Justin Drake plans to start writing an executable specification next, which will ultimately be reduced to about 1,000 lines of Python code.
In addition, two client development teams (the Zeam team in India and the Lambda team in South America) have expressed interest in developing Beam Chain clients.
