如今，最新的以太坊新闻包括下一个升级Fusaka，引起了很多关注

3月4日，该网络客户Nethermind协议的团队负责人MarekMoraczyński吹捧了即将升级的一些核心以太坊改进建议（EIPS）。

The anticipation for the next Ethereum upgrade, Fusaka, is heating up as we speak. And to keep the community in the loop, Marek Moraczyński, the team lead for the network’s client Nethermind protocol, decided to highlight some of the core EIPs that will be accompanying the upcoming upgrade.

在我们讲话时，对下一个以太坊升级Fusaka的期望正在加热。为了使社区保持循环，该网络客户Nethermind协议的团队负责人Mareksoczyński决定突出一些将伴随即将进行的升级的核心EIP。

Taking to a recent blog post, Moraczyński pointed out that the year 2024 is quickly slipping by, and with it, the window of opportunity to integrate the Fusaka upgrade is rapidly closing.

莫拉辛斯基（Moraczyński）在最近的博客文章中指出，2024年迅速滑行，随之而来的是集成Fusaka升级的机会之窗正在迅速关闭。

On this basis, he urged the team behind the hard fork to hurry up in finalizing the scope of the upgrade.

在此基础上，他敦促艰难的叉子背后的团队快点完成升级范围。

According to the post, EIP-7594, with the tag “PeerDAS – Peer Data Availability,’ is considered the most important feature to watch out for.

根据帖子，EIP-7594带有标签“ Peerdas - Peer Data Vausiability”，被认为是要注意的最重要功能。

This new EIP introduces simple Data Availability Sampling (DAS) by utilizing gossip distribution and peer requests.

这种新的EIP通过使用八卦分发和同伴请求引入了简单的数据可用性采样（DAS）。

The aim of this integration is to ease the burden on nodes.

这种整合的目的是减轻节点的负担。

Instead of requiring all nodes to download data, which might be useful for a few use cases, EIP-7594 brings additional data availability to Ethereum users.

EIP-7594不需要所有节点下载数据，这可能对一些用例有用，而是为以太坊用户带来其他数据可用性。

This, in essence, lessens the overall load on the network.

从本质上讲，这可以减少网络上的整体负载。

Moreover, it enables new use cases that necessitate handling minimal amounts of data, such as minimal __payload and transaction data.

此外，它可以实现需要处理最少数据的新用例，例如最小__ __pay和交易数据。

Another EIP that is expected to be included in the Fusaka upgrade is EIP-7692: EOF.

预计将包含在Fusaka升级中的另一个EIP是EIP-7692：EOF。

EOF is a meta EIP that compiles EIPs belonging to the EOFv1 proposal, including EIP-7480: EOF Data section access instructions and EIP-663: SWAPN, DUPN, and EXCHANGE instructions.

EOF是一种元EIP，它编译了属于EOFV1建议的EIP，包括EIP-7480：EOF数据部分访问指令和EIP-663：SWAPN，DUPN和Exchange指令。

This EIP will function in conjunction with EIP-7873 TXCREATE Transaction, which adds a TXCREATE instruction to EOF.

该EIP将与EIP-7873 TXCREATE交易结合使用，该交易为EOF添加了TXCreate指令。

This will accompany the transaction type, allowing the creation of EOF contracts from transaction data.

这将伴随交易类型，从而允许从交易数据中创建EOF合同。

The introduction of this instruction will be dependent on the transaction type and will generate an overflow exception if it's not in the valid range.

此指令的引入将取决于事务类型，如果不在有效范围内，将产生溢出异常。

This integration aims to enhance the efficiency and functionality of the EVM.

该集成旨在提高EVM的效率和功能。

The Fusaka upgrade is also expected to include EIP-7883: ModExp Gas Cost Increase.

Fusaka升级还预计还包括EIP-7883：MODEXP GAS成本增加。

This EIP modifies the ModExp precompile pricing algorithm that was initially introduced in EIP-2565.

该EIP修改了最初在EIP-2565中引入的MODEXP预编码算法。

The goal of this change is to adjust the relative gas cost of performing modular exponentiation in the precompile.

这种变化的目的是调整执行预编译中模块化凸的相对气体成本。

The updated formula will take into account the size of the modulus and the input values.

更新的公式将考虑模量和输入值的大小。

In addition to these three EIPs, Moraczyński also mentioned EIP-7825: Transaction Gas Limit Cap, EIP-7212: Precompile for secp256r1 Curve Support, and EIP-7823: Set upper bounds for MODEXP.

除了这三个EIP外，Moraczyński还提到了EIP-7825：交易气体限制，EIP-7212：SECP256R1曲线支持的预编译和EIP-7823：设置MODEXP的上限。

It is worth noting that most of these EIPs were deferred from the soon-to-launch Pectra hard fork.

值得注意的是，这些EIP中的大多数是从即将发出的Pectra Hard Fork中延迟的。

The Pectra hard fork is set to introduce several new features to the Ethereum network, including the integration of Verkle trees and the EVM Object Format (EOF).

Pectra Hard Fork设置为以太坊网络引入多个新功能，包括Verkle树的集成和EVM对象格式（EOF）。

The Fusaka upgrade will also see the launch of PeerDAS, a new networking protocol that is designed to improve the scalability of the network.

Fusaka升级还将看到Peerdas的启动，Peerdas是一种新的网络协议，旨在提高网络的可扩展性。

The introduction of PeerDAS has been a hot topic of discussion in the crypto sphere, especially with input from Ethereum co-founder Vitalik Buterin.

Peerdas的引入一直是加密领域讨论的热门话题，尤其是在以太坊联合创始人Vitalik Buterin的意见中。

Buterin once stated that Fusaka needs to get on a Layer-1 (L1) with PeerDAS.

Buterin曾经说过Fusaka需要与Peerdas一起使用1层（L1）。

According to his calculations, the best-case scenario would be to have the event occur around epoch 222464 with a 48/72 blob target/limit.

根据他的计算，最好的情况是将事件发生在Epoch 222464附近，其目标是48/72 BLOB目标/限制。

The implementation of PeerDAS is crucial for scaling the Ethereum network; therefore, developers are anticipating its arrival.

Peerdas的实施对于扩展以太坊网络至关重要。因此，开发人员正在期待它的到来。

The new protocol will allow for more efficient use of the network's bandwidth, which is especially important as the network continues to grow.

新协议将允许更有效地利用网络的带宽，随着网络的不断增长，这一点尤为重要。

The introduction of PeerDAS is just one part of a broader effort to scale the Ethereum network.

Peerdas的引入只是扩展以太坊网络的更广泛努力的一部分。

Developers are also working on other initiatives, such as the integration of Verkle trees and the EVM Object Format (EOF).

开发人员还在研究其他计划，例如Verkle树的整合和EVM对象格式（EOF）。

These innovations are expected to improve the performance and efficiency of the network, paving the way for even more use cases.

这些创新有望提高网络的性能和效率，为更多用例铺平了道路。

EOF has already entered an advanced stage of implementation, where it can enhance both EVM functionality and ZK-provability.

EOF已经进入了实施的高级阶段，它可以增强EVM功能和ZK可提供性。

Also, it has the potential to provide a structured path for future EVM improvements.

此外，它有可能为未来的EVM改进提供结构化的途径。

After several months of waiting, Ethereum’s Pectra hard fork will finally go live on the Sepolia testnet on March 5.

经过几个月的等待，以太坊的pectra硬叉终于将于3月5日在Sepolia Testnet上线。

The development team confirmed this Ethereum news in a recently unveiled timeline.

开发小组在最近揭幕的时间表中确认了这一以太坊新闻。

The devs made this decision during the 206th All Core Developers Execution (ACDE) calls held on February

开发人员在2月举行的第206个所有核心开发人员执行（ACDE）中做出了这一决定