Fuel手册-更新中 (The Fuel Book)-updating
  • 0.Fuel手册 (The Fuel Book)
  • 1. 开发者快速上手 (Developer Quickstart)
    • 1.1构建智能合约 (Building A Smart Contract)
    • 1.2 构建前端 (Building a Frontend)
  • 2.准备开始 (Getting Started)
    • 2.1为什么是Fuel (Why Fuel)
    • 2.2Fuel是什么? (What is Fuel?)
      • 2.2.1 Fuel工具链 (The Fuel Toolchain)
    • 2.3 模块化运动 (Modular Movement)
      • 2.3.1 单片架构 (Monolithic Architecture)
      • 2.3.4 什么是模块化执行层 (What is a Modular Execution Layer)
    • 2.4 Fuel设置 (Fuel Configurations)
      • 2.4.1 作为汇总的Fuel (Fuel as a roll-up)
      • 2.4.2 作为L1的Fuel (Fuel as an L1)
      • 2.4.3 作为状态通道的Fuel (Fuel as a state channel)
      • 2.4.4 作为侧链的Fuel (Fuel as a sidechain)
  • 3. 技术 (Technology)
    • 3.1 并行交易执行(Parallel Transaction Execution)
    • 3.2欺诈证明 (Fraud Proofs)
  • 4. Fuel虚拟机 (The FuelVM)
    • 4.1合约和调用模型(Contract and Call Model)
    • 4.2内存模式 (Memory Mode)
    • 4.3多重原生资产(Multiple Native Assets)
    • 4.4FuelVM和EVM, 轻松搞明白(FuelVM vs. EVM, Explained)
  • 5.Sway语言 (Sway Language)
    • 5.1 Sway设计哲学 (Sway Design Philosophy)
    • 5.2 Sway的安全性 (Sway Safety)
  • 6.开发者看这里(For Developers)
    • 6.1Sway程序示例 (Sway Application Examples)
    • 6.2 网络 (Networks)
      • 6.2.1 `beta-3`测试网 (The `beta-3` testnet)
      • 6.2.2 `beta-2`测试网 (The `beta-2` testnet)
      • 6.2.3 `beta-1` 测试网 (beta-1 testnet)
    • 6.3 运行一个本地Fuel节点 (Running a local Fuel node)
    • 6.4 Sway语言 (Sway Language) 🌴
    • 6.5 Typescript SDK
    • 6.6 Rust SDK
    • 6.7 Fuel索引器 (Fuel Indexer)
    • 6.8 水龙头和区块浏览器 (Faucet and Block Explorer)
    • 6.9 Fuelup
    • 6.10 Fuel GraphQL API
  • 7. Fuel术语 (Fuel Glossary)
Powered by GitBook
On this page
  1. 2.准备开始 (Getting Started)

2.3 模块化运动 (Modular Movement)

Previous2.2.1 Fuel工具链 (The Fuel Toolchain)Next2.3.1 单片架构 (Monolithic Architecture)

Last updated 2 years ago

Although L2s have opened up a margin of cost reduction for access to the Ethereum ecosystem, the total throughput increase has been modest at best (with both optimistic and ZK approaches). And in times of high traffic on Ethereum, L2s have failed to keep costs low, often rising to several dollars per transaction.

尽管 L2 为访问以太坊生态系统开辟了降低成本的空间,但总吞吐量的增长充其量仅能适度(采用OP 和 ZK 方法)。在以太坊的高流量时期,L2 无法保持低成本,每笔交易通常会上升到几美元。

As a community, if we want to achieve true global access to blockchain technology, we cannot settle for a modest reduction in fees. We need dramatic change. Change that not only reduces waste and inefficiency but opens up new use cases never before seen in the blockchain space.

作为一个社区,如果我们想要实现真正的全球访问区块链技术,我们就不能满足于适度降低费用。我们需要戏剧性的改变。那种不仅可以减少浪费和低效率,还可以开辟区块链领域前所未有新用例的改变。

There is an ongoing colossal shift happening in layer-1 (L1) blockchain architectures. We are moving away from a monolithic design, where consensus, data availability, and execution are tightly coupled (e.g. today's Ethereum), to a modular future, where execution is separated from data availability and consensus (e.g. tomorrow's Eth2, or Celestia). This separation allows for specialization at the base layer, delivering a significant increase in bandwidth capacity.

第 1 层 (L1) 区块链架构正在发生巨大的转变。我们正在从共识、数据可用性和执行紧密耦合的整体设计(例如今天的以太坊)转向模块化的未来,其中执行与数据可用性和共识分开(例如 Eth2 或 Celestia)。这种分离允许在基础层就进行专业化,从而显着增加带宽容量。

为什么要模块化 (Why Modular?)

A modular blockchain architecture does not inherently enable scaling. The properties that are derived as a result are what make this possible. Fuel was built for fraud proofs, enabling trust-minimized light clients, enabling high security without requiring high resource usage.

模块化区块链架构本身最开始并不是为了支持扩展。结果(一系列)派生的属性使这成为可能。 Fuel 是为欺诈证明而构建的,支持信任最小化的轻客户端,在不需要高资源使用的情况下实现高安全性。

安全与资源需求 (Security vs. Resource Requirements)

fuel1

Alternatively, a user can run a light client, also known as an honest majority light client. Instead of downloading all blocks to verify transactions, light clients only download block headers and check their proof-of-work (PoW), assuming the heaviest chain is valid. Honest majority light-clients that trust that a majority of validators are honest and will reject fraudulent transactions.

又或者,用户可以运行轻客户端,也称为诚实多数轻客户端。假设最重的链是有效的,轻客户端不会下载所有块来验证交易,而是只下载区块头并检查它们的工作量证明 (PoW)。诚实多数轻客户端相信大多数验证者是诚实的,并且会拒绝欺诈交易。

The amount of computational resources and storage needed to run a light client is lower than a full node by several orders of magnitude.

运行轻客户端所需的计算资源和存储量比全节点低几个数量级。

An easy way to remember the difference: An honest majority light client is only secure if most validators are honest. A full node is honest even if all validators are not honest.

记住区别的一种简单方法:只有大多数验证者都是诚实的,诚实的多数轻客户端才是安全的。即使所有验证者都不诚实,全节点也是诚实的。

By running a full node, you get the maximum security of verifying transactions but also have to spend a lot of computational resources to achieve this. Because a light client doesn’t need to run 24/7 and doesn’t interact directly with the chain, the computational requirement is much lower, but you also get low security.

通过运行一个全节点,你可以获得验证交易的最大安全性,但也必须花费大量的计算资源来实现这一点。因为轻客户端不需要 24/7 全天候运行并且不直接与链交互,所以计算要求低得多,但安全性也很低。

信任最小化客户端 (Trust-Minimized Light Clients)

Fuel’s design lets light clients say that blocks are valid through fraud proofs. This eliminates the need for a trusted party while maintaining low resource requirements and achieving high security. For monolithic chains like Ethereum, there is an ideological incentive to keep the computation requirements for full nodes low to allow users to be truly sovereign.

Fuel 的设计让轻客户可以通过欺诈证明说区块是有效的。这消除了对可信方的需求,同时保持低资源需求并实现高安全性。对于像以太坊这样的单片链,有一种执念般的动机是保持对全节点的低计算要求,以允许用户真正拥有主权。

Because Fuel was built for fraud proofs, the resource requirements for full nodes can be higher, thus increasing bandwidth capacity while still allowing users to verify the chain through trust-minimized light clients.

由于 Fuel 是为欺诈证明而构建的,因此全节点的资源要求可能更高,从而增加带宽容量,但同时仍然允许用户通过信任最小化的轻客户端来验证链。

In a monolithic architecture, users must choose between high security and high computational resource usage and trusted security and low computational resource usage. For example, , a type of node that offers maximum security by downloading and verifying every single transaction. By running a full node, users don’t have to trust that the chain is valid and can instead verify themselves. However, running a full node requires a lot of disk space and non-negligible CPU allocation and can take days to sync the blockchain from genesis.

在单片架构中,用户必须在高安全性和高计算资源使用率与可信安全性和低计算资源使用率之间做出选择。例如,,通过节点提供最大安全性的节点下载并验证每笔交易。通过运行一个全节点,用户不必相信链是有效的,却可以验证自己。然而,运行一个全节点需要大量的磁盘空间和不可忽略的 CPU 分配,并且可能需要几天时间才能从创世纪同步区块链。

graph showing security versus resource requirements on running full node, honest-majority light client, and trust-minimized light client
Ethereum was designed to allow consumer-grade hardware to be able to run a full node
以太坊想让消费级硬件能够运行全节点