以太坊联合创始人Vitalik Buterin认为，区块链的长期弹性和可扩展性在使其简单的铰链上，例如比特币

在5月3日的博客文章中，他描述了“从现在起5年的以太坊如何变得像比特币一样简单”。

Ethereum co-founder Vitalik Buterin envisions an instance of Ethereum's consensus layer code and a portion of the execution layer code. Together, they span less than 1,000 lines of code, aiming to make it simple enough for a high-school student to comprehend. In contrast, the code for a single large Unix program can exceed 1 million lines.

以太坊联合创始人Vitalik Buterin设想了以太坊共识层代码和执行层代码的一部分的实例。它们共同涵盖了不到1,000行的代码，旨在使高中生的理解足够简单。相比之下，单个大型UNIX程序的代码可能超过100万行。

Simplicity is often underestimated in programming. It renders programs more accessible, reduces the cost of creating new infrastructure and maintaining existing infrastructure, and minimizes the risk of bugs.

在编程中通常低估了简单性。它使程序更容易访问，降低了创建新的基础架构和维护现有基础架构的成本，并最大程度地减少了错误的风险。

Recently, Ethereum has been making good progress in becoming more robust, thanks to the integration of proof-of-stake (PoS) and Zero-Knowledge Succinct Non-Interactive Argument of Knowledge (zk-SNARK). However, we haven't yet sufficiently prioritized simplicity of design, which has led to additional costs.

最近，由于综合出验证证明（POS）和零知识简洁的知识论点（ZK-SNARK），以太坊一直在变得更加健壮。但是，我们尚未充分优先考虑设计的简单性，这导致了额外的成本。

Historically, Ethereum has often neglected this aspect (sometimes due to my own decisions), contributing to excessive development expenditure, various security risks, and a relative lack of interoperability with external R&D culture, often in pursuit of benefits that have proven illusory.

从历史上看，以太坊经常忽略了这一方面（有时是由于我自己的决定），导致了过度发展支出，各种安全风险以及与外部研发文化的相对缺乏互操作性，通常是为了追求证明虚幻的利益。

I believe that over the next 3-5 years, we can and should make significant progress in this direction. We can aim to make Ethereum 5 years from now have consensus-critical code that is close to as simple as Bitcoin, which is something that many people have set as a goal for a long time.

我相信，在接下来的3 - 5年中，我们可以并且应该在这个方向上取得重大进展。我们的目标是使以太坊从现在起5年后具有与比特币一样简单的共识准则，这是许多人长期以来设定的目标。

One of the best things about Bitcoin is how beautifully simple the protocol is. A smart high-school student can read the protocol and understand the main concepts and architecture of the protocol.

关于比特币最好的事情之一是协议的简单非常简单。智能高中生可以阅读协议并了解协议的主要概念和架构。

We want to be able to say the same about Ethereum. I think we can get close.

我们希望能够对以太坊说同样的话。我认为我们可以接近。

3-slot finality will allow us to eliminate concepts like slots, epochs, and sync committees from the common view. A basic implementation of 3-slot finality can be done in about 200 lines of code, which is simpler than the 1,008 lines of code for the main Harvest aggregator contract.

3插槽的最终性将使我们能够从共同的角度消除诸如老虎机，时代和同步委员会之类的概念。可以在大约200行代码中完成三槽终止的基本实现，这比主要收获聚合器合同的1,008行代码简单。

We will also have fewer active validators at a time, which will make it safer to use simpler implementations of the fork choice rule.

我们一次还将拥有更少的活动验证器，这将使使用叉选择规则的简单实现更加安全。

We will use STARK-based aggregation protocols for efficient validator slashing aggregation, and anyone can be an aggregator. The complexity of the aggregation cryptography itself is significant, but it is at least highly encapsulated complexity, which has much lower systemic risk toward the protocol.

我们将使用基于Stark的聚合协议进行有效的验证器削减聚合，任何人都可以成为聚合器。聚集密码学本身的复杂性很重要，但至少是高度封装的复杂性，对协议的系统风险要低得多。

This will likely enable a simpler and more robust P2P architecture. We can also rethink and simplify several facets, such as validator entry and exit, inactivity leak, and more, both by reducing line-of-code (LoC) count and by creating more legible guarantees.

这可能会启用更简单，更强大的P2P体系结构。我们还可以通过减少编码线（LOC）计数并创建更清晰的保证，重新考虑和简化了几个方面，例如验证器进入和退出，不活动泄漏等等。

The consensus layer is relatively disconnected from Ethereum Virtual Machine (EVM) executions, providing relatively wide latitude for us to make improvements.

共识层与以太坊虚拟机（EVM）的执行相对脱节，为我们提供了相对较宽的纬度以进行改进。

We can also make the execution layer simpler. Last month, I proposed replacing EVM contract language with RISC-V to boost efficiency by up to 100x.

我们还可以使执行层更简单。上个月，我提议替换与RISC-V的EVM合同语言，以提高效率高达100倍。

The adoption of RISC-V will also increase simplicity, as the RISC-V spec is absurdly simple compared to the EVM. Of course, we need to ensure that we preserve backwards compatibility for existing applications.

RISC-V的采用也将提高简单性，因为与EVM相比，RISC-V规格非常简单。当然，我们需要确保我们为现有应用程序保留向后兼容。

The first thing that is important to understand is: there isn’t one single way to delineate what is the “Ethereum codebase” (even within a single client).

重要的是要理解的第一件事是：没有一种方法可以描述“以太坊代码库”（即使在单个客户端中）是什么。

The goal is to minimize the green area, by moving code to the yellow area, which indicates code that is very valuable for understanding and interpreting the chain today, or for optimal block building, but is not part of consensus.

目的是通过将代码移至黄色区域来最大程度地减少绿色区域，这表明代码对于理解和解释当今的链条或最佳块构建非常有价值，但不是共识的一部分。

We can think of this process as how Apple achieves long-term backwards compatibility through translation layers.

我们可以将这个过程视为苹果如何通过翻译层实现长期倒退的兼容性。

Importantly, the orange and yellow areas are encapsulated complexity; anyone looking to understand the protocol can skip them, implementations of Ethereum are free to skip them, and any bugs in those areas do not pose consensus risks.

重要的是，橙色区域和黄色区域是封装的复杂性。任何想要了解该协议的人都可以跳过它们，以太坊的实现可以跳过它们，并且这些领域的任何错误都不会构成共识的风险。

This means that code complexity in the orange and yellow areas has far fewer downsides compared to code complexity in the green area.

这意味着，与绿色区域的代码复杂性相比，橙色和黄色区域的代码复杂性较少。

To reduce the green area, we can take the following steps:

为了减少绿色区域，我们可以采取以下步骤：

Phase 1: New precompiles will be written in RISC-V.

第1阶段：新的预编译将以RISC-V编写。

Phase 2: Developers will have the option to write contracts in RISC-V.

第2阶段：开发人员将可以选择在RISC-V中签订合同。

Phase 3: All precompiles will be replaced with RISC-V implementations through a hard fork.

第3阶段：所有预编译将通过硬叉替换为RISC-V实现。

Phase 4: We will implement an EVM interpreter in RISC-V and push it onchain as a smart contract.

第4阶段：我们将在RISC-V中实施EVM解释器，并将其作为智能合约推动。

This way, Ethereum consensus will natively understand only RISC-V.

这样，以太坊共识将仅本地理解RISC-V。

We can also share one standard across different parts of the stack.

我们还可以在堆栈的不同部分共享一个标准。

For instance, we can use a single erasure code for data availability sampling, P2P broadcasting, and distributed history storage. This will minimize the total lines of code, increase efficiency, and ensure verifiability.

例如，我们可以使用单个擦除代码进行数据可用性采样，P2P广播和分布式历史记录存储。这将最大程度地降低代码的总线路，提高效率并确保可验证性。

Similarly, we can have one shared serialization format across the three

同样，我们可以在这三种方面具有一种共享的序列化格式