查看原文
其他

【官方】Fil v16升级社区AMA常见问题解答;EVM相容性是重要的优先事项,将在2022年秋季作为FVM里程碑M2.1发布


Q: Which version of Lotus will run the FVM?
问:哪个版本的 Lotus 可运行 FVM (Filecoin 虚拟机)?
 
A: Both Lotus versions v1.16.0 and v1.17.0 will support the FVM.  Both versions are currently available as release candidates; full versions will be released prior to the July 6 upgrade.
答:两种Lotus 版本 v1.16.0 和 v1.17.0 都将支持FVM。这两个版本目前都是预发布版本;完整版本将在 7 月 6 日升级之前发布。
 
Q: When do I need to upgrade to the latest version of Lotus?
问:我什么时候需要升级到最新版本的 Lotus?
 
A: You will need to have upgraded your node by the epoch 1960320, which will occur at approximately 14:00 UTC on July 6th, 2022.  For the official network upgrade notice, please see HERE.  For the community network discussion, please see HERE. 
答:您需要于epoch 1960320 前升级您的节点, 时间大约是 2022 年 7 月 6 日14:00 UTC。有关官方网络升级通知,请参阅此处。有关社区网络讨论,请参阅此处。
 
Q: Will the FVM impact gas fees or network throughput?
问:FVM 会影响燃料费用或网络吞吐量吗?
 
A: Yes and no.  With the FVM introducing a WASM bytecode, the network will now be able to price the actual cost of execution of actor/smart contract logic.  To support this, FIP0032 introduced three new gas elements: execution gas, syscall gas, and extern gas. Network base fee- which calculates gas costs- will remain unchanged.  However, to ensure no spike in base fee during the introduction of the FVM, new gas parameters were tested extensively by the FVM engineering team (see: HERE and HERE).  The CrytpoEconLab also performed an analysis to ensure the continued stability of the network.
答:也是也不是。随着 Filecoin 虚拟机 引入 WASM 字节码,网络现在可以对执行智能合约(actor)逻辑的实际成本进行定价。为支持这应用,FIP0032 引入了三种新的燃料:执行燃料、系统调用燃料和外部燃料。计算燃料成本的网络基础费用将保持不变。但为了确保在引入 FVM 期间基本费用不会飙升,FVM 工程团队对新的燃料参数进行了广泛的测试。CrytpoEconLab 还进行了分析,以确保网络的持续稳定性。
 
Q: What work are we doing to support FVM <> EVM compatibility?
问:我们正在做哪些工作来支援 FVM <> EVM 相容性?
 
A: Many community members have indicated that EVM compatibility is a significant priority.  As such, EVM compatibility will now be shipped as FVM milestone M2.1 in the autumn of 2022.  This work will bedeployed incrementally, in testnets, with the support of community partners.  The FVM team has already completed a significant amount of research and has a working EVM bytecode execution! A high-level demo will be delivered at FIL Toronto.
答:许多社区成员表示 EVM 相容性是重要的优先事项。因此,现在EVM 相容性将在 2022 年秋季作为 FVM 里程碑 M2.1 发布。这项工作将在社区合作伙伴的支持下逐步部署在测试网中。FVM 团队已经完成了大量的研究,并实现一个可用的 EVM 字节码执行环境!我们在 FIL Toronto 将提供高层级演示。
 
Q: Will EVM actors be able to dispatch methods to native FVM builtin actors? What functionality isn’t available to EVM actors that would be available to FVM actors?
问:EVM actor 是否能够将方法调用原生 FVM 的内置 actor?哪些功能不适用于 EVM actor,而 FVM actor可以使用?
 
A: EVM actors can call FVM actors, and vice versa.  All actors will interface in the same way, and additional Solidity libraries are already being prepared to reduce friction between actors. The primary difference in functionality is that the FVM is additionally able to provide an actor “upgrade” capability and is able to make better use of existing IPLD functionalities.  For example, the FVM will be able to cheaply send an immutable copy of its state-tree to another actor, which the EVM cannot do. Though some of these features can be made available to EVM actors through precompiles, their usefulness and limitations will need to be further studied on a case-by-case basis.
答:EVM actors 可以调用 FVM actors,反之亦然。所有actors都将以相同的方式互动,并且已经备好额外的Solidity 库来减少actor之间的冲突。其功能上的主要区别在于,FVM 能够提供actor“升级”功能,并且能够更有效地使用现有的 IPLD 功能。例如,FVM 将能廉价地将其状态树的不可变副本发送给另一个actor, 这部分EVM 则无法做到。虽然其中一些功能可以通过预编提供给 EVM actor,但它们的实用性和局限需要依具体情况进一步研究。
 
Q: Are there any new security vulnerabilities that need to be considered when forking a contract from an EVM blockchain to an FVM actor?
问:在将合约从 EVM 区块链分叉到 FVM actor时,是否需要考虑任何新的安全漏洞?
 
A: No.  To prevent security vulnerabilities from arising, there is a ‘double’ sandbox in place: the EVM sandbox, and the FVM/WASM sandbox. However, it is important to remember that bugs can occur at any level.   We also need to be mindful of potential “dissonances”, or mismatches, between EVM and FVM/WASM that could create gray zones.
答:不需要。为了防止出现安全漏洞,设有一个‘双重’沙盒:EVM 沙盒和 FVM/WASM 沙盒。但是,重要的是要记住错误可能发生在任何层级。我们还需要注意 EVM 和 FVM/WASM 之间可能产生灰色区域的潜在“不和谐”或不匹配。


您可能也对以下帖子感兴趣

文章有问题?点此查看未经处理的缓存