New translations introduction.mdx (Chinese Simplified)

graphprotocol · benface · Jan 28, 2022 · Jan 28, 2022 · Jan 28, 2022 · Jan 28, 2022
commit 25bdd2f08e43171bae9a3335a712c065e09d16bd
@@ -1,49 +1,47 @@
 ---
-title: 介绍
+title: Introduction
 ---
 
-本页将解释什么是 The Graph，以及你如何开始。
+This page will explain what The Graph is and how you can get started.
 
-## 什么是 The Graph
+## What The Graph Is
 
-The Graph 是一个去中心化的协议，用于索引和查询区块链的数据，首先是从以太坊开始的。 它使查询那些难以直接查询的数据成为可能。
+The Graph is a decentralized protocol for indexing and querying data from blockchains, starting with Ethereum. It makes it possible to query data that is difficult to query directly.
 
-像 [Uniswap](https://uniswap.org/)这样具有复杂智能合约的项目，以及像 [Bored Ape Yacht Club](https://boredapeyachtclub.com/) 这样的 NFTs 倡议，都在以太坊区块链上存储数据，因此，除了直接从区块链上读取基本数据外，真的很难。
+Projects with complex smart contracts like [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it really difficult to read anything other than basic data directly from the blockchain.
 
-在 Bored Ape Yacht Club 的案例中，我们可以对 [合约](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code)进行基本的读取操作，比如获得某个 Ape 的所有者，根据他们的 ID 获得某个 Ape 的内容 URI，或者总供应量，因为这些读取操作是直接编入智能合约的，但是更高级的现实世界的查询和操作，比如聚合、搜索、关系和非粗略的过滤是不可能的。 例如，如果我们想查询某个地址所拥有的 apes，并通过它的某个特征进行过滤，我们将无法通过直接与合约本身进行交互来获得该信息。
+In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply, as these read operations are programmed directly into the smart contract, but more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are not possible. For example, if we wanted to query for apes that are owned by a certain address, and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
 
-为了获得这些数据，你必须处理曾经发出的每一个 [`传输`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) 事件，使用 Token ID 和 IPFS 的哈希值从 IPFS 读取元数据，然后将其汇总。 即使是这些类型的相对简单的问题，在浏览器中运行的去中心化应用程序（dapp）也需要**几个小时甚至几天** 才能得到答案。
+To get this data, you would have to process every single [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) event ever emitted, read the metadata from IPFS using the Token ID and IPFS hash, and then aggregate it. Even for these types of relatively simple questions, it would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer.
 
-你也可以建立你自己的服务器，在那里处理交易，把它们保存到数据库，并在上面建立一个 API 终端，以便查询数据。 然而，这种选择是资源密集型的，需要维护，会出现单点故障，并破坏了去中心化化所需的重要安全属性。
+You could also build out your own server, process the transactions there, save them to a database, and build an API endpoint on top of it all in order to query the data. However, this option is resource intensive, needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
 
-**为区块链数据编制索引真的非常非常难。**
+**Indexing blockchain data is really, really hard.**
 
-区块链的属性，如最终性、链重组或未封闭的区块，使这一过程进一步复杂化，并使从区块链数据中检索出正确的查询结果不仅耗时，而且在概念上也很难。
+Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further, and make it not just time consuming but conceptually hard to retrieve correct query results from blockchain data.
 
-The Graph 通过一个去中心化的协议解决了这一问题，该协议可以对区块链数据进行索引并实现高性能和高效率的查询。 这些 API（索引的 "子图"）然后可以用标准的 GraphQL API 进行查询。 今天，有一个托管服务，也有一个具有相同功能的分去中心化协议。 两者都由 [](https://github.com/graphprotocol/graph-node)Graph Node
+The Graph solves this with a decentralized protocol that indexes and enables the performant and efficient querying of blockchain data. These APIs (indexed "subgraphs") can then be queried with a standard GraphQL API. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
 
-的开放源码实现支持。
+## How The Graph Works
 
-## The Graph 是如何工作的
+The Graph learns what and how to index Ethereum data based on subgraph descriptions, known as the subgraph manifest. The subgraph description defines the smart contracts of interest for a subgraph, the events in those contracts to pay attention to, and how to map event data to data that The Graph will store in its database.
 
-Graph 根据子图描述（称为子图清单）来学习什么以及如何为以太坊数据建立索引。 子图描述定义了子图所关注的智能合约，这些合约中需要关注的事件，以及如何将事件数据映射到 The Graph 将存储在其数据库中的数据。
+Once you have written a `subgraph manifest`, you use the Graph CLI to store the definition in IPFS and tell the indexer to start indexing data for that subgraph.
 
-一旦你写好了 `子图清单 `，你就可以使用 Graph CLI 将该定义存储在 IPFS 中，并告诉索引人开始为该子图编制索引数据。
-
-这张图更详细地介绍了一旦部署了子图清单，处理以太坊交易的数据流。
+This diagram gives more detail about the flow of data once a subgraph manifest has been deployed, dealing with Ethereum transactions:
 
 ![](/img/graph-dataflow.png)
 
-流程遵循这些步骤：
+The flow follows these steps:
 
-1. 一个去中心化的应用程序通过智能合约上的交易向以太坊添加数据。
-2. 智能合约在处理交易时，会发出一个或多个事件。
-3. Graph 节点不断扫描以太坊的新区块和它们可能包含的子图的数据。
-4. Graph 节点在这些区块中为你的子图找到 Ethereum 事件并运行你提供的映射处理程序。 映射是一个 WASM 模块，它创建或更新 Graph Node 存储的数据实体，以响应 Ethereum 事件。
-5. 去中心化的应用程序使用节点的[GraphQL 端点](https://graphql.org/learn/)，从区块链的索引中查询 Graph 节点的数据。 Graph 节点反过来将 GraphQL 查询转化为对其底层数据存储的查询，以便利用存储的索引功能来获取这些数据。 去中心化的应用程序在一个丰富的用户界面中为终端用户显示这些数据，他们用这些数据在以太坊上发行新的交易。 就这样周而复始。
+1. A decentralized application adds data to Ethereum through a transaction on a smart contract.
+2. The smart contract emits one or more events while processing the transaction.
+3. Graph Node continually scans Ethereum for new blocks and the data for your subgraph they may contain.
+4. Graph Node finds Ethereum events for your subgraph in these blocks and runs the mapping handlers you provided. The mapping is a WASM module that creates or updates the data entities that Graph Node stores in response to Ethereum events.
+5. The decentralized application queries the Graph Node for data indexed from the blockchain, using the node's [GraphQL endpoint](https://graphql.org/learn/). The Graph Node in turn translates the GraphQL queries into queries for its underlying data store in order to fetch this data, making use of the store's indexing capabilities. The decentralized application displays this data in a rich UI for end-users, which they use to issue new transactions on Ethereum. The cycle repeats.
 
-## 下一步
+## Next Steps
 
-在下面的章节中，我们将更详细地介绍如何定义子图，如何部署它们，以及如何从 Graph 节点建立的索引中查询数据。
+In the following sections we will go into more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
 
-在你开始编写你自己的子图之前，你可能想看一下 Graph 浏览器，探索一些已经部署的子图。 每个子图的页面都包含一个操作面板，让你用 GraphQL 查询该子图的数据。
+Before you start writing your own subgraph, you might want to have a look at the Graph Explorer and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.