以太坊的Fusaka Hard Fork預計將在今年的第三或第四季度舉行

根據以太坊基金會官員的說法。以太坊基金會在4月28日的帖子中聯合執行董事TomaszKajetanstańczak表示，該組織的目標是在第三季度或第四季度部署Fusaka Ethereum網絡升級

Ethereum’s Fusaka hard fork is expected to take place in the third or fourth quarter of this year, according to an Ethereum Foundation official.

一位以太坊基金會官員稱，以太坊的Fusaka Hard Fork預計將在今年的第三或第四季度舉行。

In an April 28 X post, Ethereum Foundation co-executive director Tomasz Kajetan Stańczak said that the organization is aiming to deploy the Fusaka Ethereum network upgrade in Q3 or Q4 2025. Still, the exact rollout schedule has not been decided yet.

在4月28日的X帖子中，以太坊基金會聯合執行董事TomaszKajetanstańczak表示，該組織的目標是在第三季度或第4季度2025年部署Fusaka Ethereum Network升級。儘管如此，確切的推出時間表尚未決定。

Stańczak said a controversial implementation of the EVM object format (EOF) upgrade for the Ethereum Virtual Machine (EVM) was expected to be a part of the Fusaka network upgrade, which Ethereum core developer Tim Beiko later ruled out.

斯坦卡克說，以太坊虛擬機（EVM）的EVM對象格式（EOF）升級的有爭議實施預計將成為Fusaka Network升級的一部分，以太坊核心開發商Tim Beiko後來被裁定。

EOF was removed from the Fusaka network upgrade today, merging the upgrade without it, as there was technical uncertainty around its impact, which may delay the Fusaka rollout, impacting the roadmap.https://t.co/b73782y89a

EOF今天已從Fusaka網絡升級中刪除，在沒有它的情況下將升級合併，因為其影響圍繞其影響，這可能會延遲Fusaka的推出，從而影響Roadmap.https.https：//t.co/b73782y89a

— Tim Beiko (@TimBeiko) April 28, 2024

- 蒂姆·貝科（@timbeiko）2024年4月28日

The EVM is the software that runs Ethereum smart contracts. EOF would implement a series of protocol changes, known as Ethereum improvement proposals (EIPs), with profound implications for how it operates. EOF introduces an extensible and versioned container format for the smart contract bytecode that is verified once at deployment, separating code and data for efficiency gains.

EVM是運行以太坊智能合約的軟件。 EOF將實施一系列協議更改，稱為以太坊改進建議（EIPS），對其運作方式產生了深遠的影響。 EOF為智能合約字節碼引入了可擴展且版本的容器格式，該格式在部署時經過驗證，將代碼和數據分開以獲得效率提高。

This structure streamlines EVM operation, allowing for higher efficiency and lower processing overhead. This upgrade would also result in a cleaner developer environment and easier-to-understand deployed smart contracts.

該結構簡化了EVM操作，允許提高效率和較低的處理開銷。此升級還將導致更清潔的開發人員環境和易於理解部署的智能合約。

Don’t JUMP, RJUMP instead!

不要跳，而是！

EIP-4200, one of the EOF EIPs, provides an alternative to the JUMP and JUMPI instructions, which allow the program to move execution to any arbitrary byte offset. This kind of execution chain leads to hard-to-spot bugs (the JUMP value being wrong in some instances may not be easy to predict) and makes it easy to hide malware in data blobs and move the execution pointer there.

EIP-4200（EIP-4200）是EOF EIPS之一，提供了跳躍和跳躍指令的替代方案，允許該程序將執行移至任何任意字節偏移。這種執行鏈會導致難以顯示錯誤（在某些情況下，跳躍值是錯誤的，可能不容易預測），並且可以輕鬆將惡意軟件隱藏在數據斑點中並將執行指針移動到其中。

This practice is known as dynamic jump, and EIP-4750 (under review) proposes disallowing dynamic JUMP/JUMPI inside EOF smart contracts, rejecting them entirely during a later phase of EOF deployment. In its current form, this EIP replaces them with call function (CALLF) and return from function (RETF) function calls. Those new instructions would ensure that destinations are hardcoded into the bytecode, but legacy pre-EOF smart contracts would be unaffected.

這種做法被稱為動態跳躍，EIP-4750（正在審查）提出了智能合約中的動態跳躍/跳躍，在EOF部署的後期完全拒絕它們。以當前形式，此EIP用呼叫函數（CALLF）替代了它們，並從功能（RETF）函數呼叫返回。這些新的說明將確保將目的地進行了硬編碼，但遺產智能合約將不受影響。

Developers who opt to use JUMP or JUMPI after the upgrade will have their bytecode go through deploy-time validation, which ensures that they can never jump into data or the middle of another instruction. This verification would take place via EIP-3670's code-validation rules, plus the jump table (EIP-3690), so every destination is checked.

升級後選擇使用跳躍或跳躍的開發人員將使其字節碼通過部署時間驗證，這確保他們永遠無法跳入數據或其他指令的中間。此驗證將通過EIP-3670的代碼驗證規則以及跳台（EIP-3690）進行，因此檢查每個目的地。

As an alternative to those functions, EOF implements RJUMP and RJUMPI instead, which require the destination to be hardcoded in the bytecode. Still, not everyone is on board with EOF implementation.

作為這些功能的替代方案，EOF代替了rjump和rjumpi，這要求目標在字節碼中進行硬編碼。儘管如此，並非每個人都在EOF實施中加入。

EOF has its haters

EOF有仇恨者

EOF is the implementation of 12 EIPs with profound implications for how smart contract developers work. Its supporters argue that it is efficient, more elegant, and allows for easier upgrades down the line.

EOF是實施12個EIP，對智能合同開發人員的工作方式產生了深遠的影響。它的支持者認為，它是高效，更優雅的，並且可以更輕鬆地升級。

Still, its detractors argue that it is over-engineered and introduces further complexity into an already complex system such as Ethereum. Ethereum developer Pascal Caversaccio lamented in a March 13 Ethereum Magicians post that “EOF is extremely complex,” as it adds two new semantics and removes and adds over a dozen opcodes. Also, he argued that it is not necessary.

儘管如此，它的批評者仍認為它是過度設計的，並將進一步的複雜性引入了以太坊等已經復雜的系統。以太坊開發人員Pascal Caversaccio在3月13日以太坊魔術師帖子中感嘆“ EOF非常複雜”，因為它添加了兩種新的語義和刪除，並增加了十幾個Opcodes。另外，他認為沒有必要。

He said all the benefits could be introduced in “more piecemeal, less invasive updates.” He added that the legacy EVM would also need to be maintained, “probably indefinitely.”

他說，所有好處都可以在“更零碎，侵入性更少的更新”中引入。他補充說，遺產EVM還需要維護“可能無限期”。

Caversaccio also explained that EOF would require a tooling upgrade, which risks introducing new vulnerabilities due to its large attack surface. Also, he said, “EVM contracts get much more complicated due to headers,” while currently empty contracts weigh just 15 bytes. Another developer raised a separate point in the thread:

Caversaccio還解釋說，EOF需要進行工具升級，這可能會由於其較大的攻擊表面而引入新的漏洞。此外，他說：“由於標題，EVM合同變得更加複雜，而目前空的合同重15個字節。另一個開發人員在線程中提出了一個單獨的點：

Caversaccio appears to be in good company in his opposition to EOF. A dedicated poll on the Ethereum polling platform ETHPulse shows that 39 voters holding a total of nearly 17,745 Ether (ETH) are opposed to the upgrade. Only seven holders of under 300 ETH voted in favor.

Caversaccio似乎在反對EOF的情況下處於良好狀態。一項針對以太坊民意調查平台Ethpulse的專門民意調查表明，總共有39名選民持有近17,745 Ether（ETH）反對升級。只有300歲以下ETH的七個持有人投票支持。