以太坊聯合創始人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

同樣，我們可以在這三種方面具有一種共享的序列化格式