Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated Chinese translation of the latest change file #70

Open
wants to merge 68 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
68 commits
Select commit Hold shift + click to select a range
f944b8f
Translate README.md to Chinese
polibee Feb 15, 2024
ddaac5f
Translate your-first-message.mdx to Chinese
polibee Feb 15, 2024
a8643f3
intro.mdx to Chinese
polibee Feb 15, 2024
4bb4d75
faq.mdx to Chinese
polibee Feb 15, 2024
ed173fc
faq.mdx to Chinese
polibee Feb 15, 2024
2c10b8b
explorer.mdx to Chinese
polibee Feb 15, 2024
1d84fc4
deploy-hyperlane-troubleshooting.mdx to Chinese
polibee Feb 15, 2024
6c272d9
deploy-hyperlane.mdx to Chinese
polibee Feb 15, 2024
f55c9f0
configuring-pi-chains.mdx to Chinese
polibee Feb 15, 2024
003d6ec
graphql-api.mdx to Chinese
polibee Feb 15, 2024
76a5106
rest-api.mdx to Chinese
polibee Feb 15, 2024
e5b4ed1
explorer-debugging.mdx to Chinese
polibee Feb 15, 2024
62041c2
unit-testing.mdx to Chinese
polibee Feb 15, 2024
c8bb16a
create-custom-hook-and-ism.mdx to Chinese
polibee Feb 15, 2024
24f8ae2
Translate deploy-hyperlane-local-agents.mdx to Chinese
polibee Feb 16, 2024
d4df3d1
Translate deploy-warp-route.mdx to Chinese
polibee Feb 16, 2024
007e8d7
Translate deploy-warp-route-UI.mdx to Chinese
polibee Feb 16, 2024
717bca5
Translate implementation-guide.mdx to Chinese
polibee Feb 16, 2024
0ef5a97
Translate run-relayer.mdx to Chinese
polibee Feb 16, 2024
7879395
Translate monitoring-alerting.mdx to Chinese
polibee Feb 16, 2024
28fd06e
Translate validator-signatures-aws.mdx to Chinese
polibee Feb 16, 2024
de928b5
Translate agent-config.mdx to Chinese
polibee Feb 16, 2024
a32de65
Translate config-reference.mdx to Chinese
polibee Feb 16, 2024
6469cb6
Translate deploy-with-terraform.mdx to Chinese
polibee Feb 17, 2024
69a4d8a
Translate run-docker-compose.mdx to Chinese
polibee Feb 17, 2024
998e1f9
Translate run-validators.mdx to Chinese
polibee Feb 17, 2024
bbec61f
Translate partials to Chinese
polibee Feb 17, 2024
4a5e33e
Translate warp-routes.mdx to Chinese
polibee Feb 17, 2024
ca96cfc
Translate protocol-overview.mdx to Chinese
polibee Feb 17, 2024
dcfedd0
Translate mailbox.mdx to Chinese
polibee Feb 17, 2024
f89d9db
Translate interchain-gas-payment.mdx to Chinese
polibee Feb 17, 2024
eee7b87
Translate relayer.mdx to Chinese
polibee Feb 17, 2024
bd755b3
Translate validators.mdx to Chinese
polibee Feb 17, 2024
a0b769b
Translate watchtowers.mdx to Chinese
polibee Feb 17, 2024
e037d7a
Translate aggregation-ISM.mdx to Chinese
polibee Feb 17, 2024
f533dc5
Translate ccip-read-ISM.mdx to Chinese
polibee Feb 17, 2024
e09e7f4
Translate economic-security.mdx to Chinese
polibee Feb 17, 2024
c487f49
Translate modular-security.mdx to Chinese
polibee Feb 17, 2024
151a975
Translate multisig-ISM.mdx to Chinese
polibee Feb 17, 2024
f3da663
Translate optimistic-ISM.mdx to Chinese
polibee Feb 17, 2024
cabd3ea
Translate routing-ISM.mdx to Chinese
polibee Feb 17, 2024
59c4c15
Translate wormhole-ISM.mdx to Chinese
polibee Feb 17, 2024
9bab53c
Translate agents.mdx to Chinese
polibee Feb 17, 2024
9ace377
Translate warp-routes.mdx to Chinese
polibee Feb 17, 2024
2658fd3
Translate interchain-gas.mdx to Chinese
polibee Feb 17, 2024
08bdd71
Translate op-stack.mdx to Chinese
polibee Feb 17, 2024
c38c7bf
Translate overview.mdx to Chinese
polibee Feb 17, 2024
bb2d670
Translate to Chinese
polibee Feb 17, 2024
f2bc579
Translate to Chinese
polibee Feb 17, 2024
8feb8ce
optimize translation
polibee Feb 17, 2024
f0800dc
Translate to Chinese
polibee Feb 17, 2024
4ccfe12
Translate to Chinese
polibee Feb 17, 2024
e1ebb8d
Translate to Chinese
polibee Feb 18, 2024
3e8da71
Translate to Chinese
polibee Feb 18, 2024
5364fe2
Translate to Chinese
polibee Feb 18, 2024
ef135fd
Translate to Chinese
polibee Feb 18, 2024
ad5a973
Translation review
polibee Feb 18, 2024
9f28c5c
update
polibee Mar 20, 2024
efd555e
Merge branch 'main' into translation
polibee Mar 22, 2024
e8f3b4b
update
polibee Mar 22, 2024
245ef00
resolve conflits
polibee Mar 22, 2024
e343d2f
update
polibee Mar 22, 2024
3a9a7d6
update new translation create-custom-hook-and-ism.mdx
polibee Mar 26, 2024
59f9f17
update new conflicts
polibee Mar 28, 2024
edcb861
Resolve conflicts
polibee Mar 29, 2024
8d1a05a
translate new update file
polibee Apr 5, 2024
5807d3d
translate new update file
polibee Apr 16, 2024
a9f415f
translate new update file
polibee Apr 29, 2024
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .idea/.gitignore

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

8 changes: 8 additions & 0 deletions .idea/modules.xml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

12 changes: 12 additions & 0 deletions .idea/v3-docs.iml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

6 changes: 6 additions & 0 deletions .idea/vcs.xml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

24 changes: 12 additions & 12 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,36 +1,36 @@
# Website
# 网站

This website is built using [Docusaurus 3](https://docusaurus.io/), a modern static website generator.
该网站使用现代静态网站生成器[Docusaurus 3](https://docusaurus.io/)制作。

## Generated Content
## 生成的内容

The `static` directory includes generated content. Please ask @yorhodes for assistance if you need to update this content.
`static`目录包含生成的内容。如果需要更新此内容,请询问 @yorhodes 寻求帮助。

Most of this is simply serialized content from `@hyperlane-xyz` NPM packages (see `devDependencies`). Eventually this should be part of the build process.
其中大部分来自 `@hyperlane-xyz` NPM 包的序列化内容(请参见`devDependencies`)。最终,这将成为构建过程的一部分。

### Installation
### 安装

```
$ yarn
```

### Local Development
### 本地开发

```
$ yarn start
```

This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
该命令启动本地开发服务器并打开浏览器窗口。大多数更改都会实时反映,而无需重启服务器。

### Build
### 构建

```
$ yarn build
```

This command generates static content into the `build` directory and can be served using any static contents hosting service.
该命令可在 `build` 目录中生成静态内容,并可使用任何静态内容托管服务进行托管。

### Deployment
### 部署

Vercel Github Action is used to deploy the website. The action is triggered on every push to the `main` branch.
使用 Vercel Github Action 来部署网站。该操作在每次推送到`main`分支时触发。

26 changes: 13 additions & 13 deletions docs/deploy-hyperlane-troubleshooting.mdx
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
# Troubleshooting
# 故障排除

## Chain configuration
## 链配置

Within your working directory, you may find a `config/` folder containing a `chains.yaml` file. This `chains.yaml` configuration file allows you to describe chain metadata for use in Hyperlane deployments or apps.
在您的工作目录中,可能会发现一个包含`chains.yaml` 文件的 `config/`文件夹。通过该`chains.yaml` 配置文件,您可以描述链元数据,以便在Hyperlane部署或应用程序中使用。

You can define a full configuration for any new chain in this file. The metadata that can be configured is defined in this [example configuration](https://github.com/hyperlane-xyz/hyperlane-monorepo/blob/main/typescript/cli/examples/chain-config.yaml). You can also find the chain metadata schema at [chainMetadataTypes.ts](https://github.com/hyperlane-xyz/hyperlane-monorepo/blob/main/typescript/sdk/src/metadata/chainMetadataTypes.ts).
您可以在此文件中为任何新链定义完整配置。可配置的元数据在此[配置示例](https://github.com/hyperlane-xyz/hyperlane-monorepo/blob/main/typescript/cli/examples/chain-config.yaml)中定义。您还可以在 [chainMetadataTypes.ts](https://github.com/hyperlane-xyz/hyperlane-monorepo/blob/main/typescript/sdk/src/metadata/chainMetadataTypes.ts)中找到链元数据模式。

Here's an example configuration for two local anvil chains:
下面是两个本地anvil chains的配置示例:

```yaml
---
Expand All @@ -30,7 +30,7 @@ anvil2:
- http: http://localhost:8555
```

You can also extend a core chain config by providing the fields to be overridden:
您还可以通过提供要重写的字段来扩展核心链配置:

```yaml
---
Expand All @@ -39,11 +39,11 @@ sepolia:
confirmations: 2
```

### Override RPC URLs
### 重写 RPC URL

You can override the RPC urls by extending the core chain config.
您可以通过扩展核心链配置来覆盖RPC网址。

In the example below, you can see how to define an array of RPCs and also adjust the retry parameters for any of them.
在下面的示例中,你可以看到如何定义RPC数组,以及如何调整其中任何一个RPC的重试参数。

```yaml
---
Expand All @@ -62,9 +62,9 @@ sepolia:
maxRequests: 10
```

### Override transaction settings
### 覆盖交易设置

Transaction overrides are any properties to include when forming transaction requests. For example:
事务重载是在形成事务请求时包含的任何属性。例如:

- `gasPrice`: number | string
- `maxFeePerGas`: number | string
Expand All @@ -73,7 +73,7 @@ Transaction overrides are any properties to include when forming transaction req
- `type`: number
- `ccipReadEnabled`: boolean

In the example below we're using a gas price of 7 gwei, hardcoding the nonce, and setting a maximum value for the base and priority fees.
在下面的示例中,我们使用的燃料价格为7gwei,对nonce进行了硬编码,并为基本费和优先费设置了最大值。

```yaml
---
Expand All @@ -87,6 +87,6 @@ sepolia:

:::warning

If you are overriding the nonce in the chain configuration, ensure you are updating the value on successful transactions.
如果要覆盖链配置中的 nonce,请确保在交易成功时更新该值。

:::
73 changes: 38 additions & 35 deletions docs/deploy-hyperlane.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,111 +4,114 @@ import DeployContractsPartial from "/docs/partials/deploy-hyperlane/_deploy-cont
import SendTestMessagesPartial from "/docs/partials/deploy-hyperlane/_send-test-messages.mdx";
import DeployWarpRoutePartial from "/docs/partials/deploy-hyperlane/_deploy-warp-route.mdx";

# Get Started
# 立即开始

Hyperlane can be deployed by anyone to any chain.
This guide covers sending your first interchain message from a new EVM chain. If you'd like to deploy to a Cosmos appchain, follow this [community-submitted guide](https://github.com/many-things/cw-hyperlane/blob/25a31818e9bf909875ab091f3884ee71bd25814f/DEPLOYMENT.md).

By the end of this guide you will have deployed and configured your Mailbox smart contract and off-chain agents, allowing developers to send interchain messages to and from your chain.
任何人都可以在任何链上部署Hyperlane。
本指南涵盖从新EVM链发送第一条链间信息。在本[指南](https://github.com/many-things/cw-hyperlane/blob/25a31818e9bf909875ab091f3884ee71bd25814f/DEPLOYMENT.md)结束时,您将部署并配置好邮箱智能合约和链外代理,从而允许开发人员向您的链发送链间消息或从您的链发送链间消息。

任何人都可以在任何链上部署Hyperlane。
本指南涵盖了从新的EVM链发送第一个链间消息。如果您想部署到Cosmos应用链,请遵循此[社区提交的指南](https://github.com/many-things/cw-hyperlane/blob/25a31818e9bf909875ab091f3884ee71bd25814f/DEPLOYMENT.md)。


:::note

This guide has been specifically made to demonstrate how to connect a chain that _already has Hyperlane on it_ to a new chain that does _not_ have Hyperlane.
本指南专门用于演示如何将已有Hyperlane的链连接到没有Hyperlane的新链上。

:::

<TerminologyPartial />

## Overview
## 概览

There are five steps in this guide:
本指南共有五个步骤:

1. [<b>Set up keys</b>](#1-set-up-keys) that you will use to deploy contracts and run validators and relayer.
2. [<b>Deploy contracts</b>](#2-deploy-contracts) to the local chain and to every remote chain with which the local chain will be able to send and receive messages.
3. [<b>Run validators and relayer </b>](#3-run-validators-relayer) using [Kurtosis](https://cloud.kurtosis.com). Validators provide the signatures needed for the Interchain Security Modules you deployed in step 2. The relayer will deliver messages between chains you deployed contracts to.
4. [<b>Send a test message</b>](#4-send-test-messages) to confirm that your relayer is able to deliver messages to and from each pair of chains
5. [<b>Deploy a warp route</b>](#5-optional-deploy-a-warp-route) to send token value, not just messages, across chains
1. [<b>Set up keys</b>](#1-set-up-keys) 您将使用它来部署合同、运行验证器和中继器。
2. [<b>Deploy contracts</b>](#2-deploy-contracts) 到本地链以及本地链可以收发信息的所有远程链。
3. [<b>Run validators and relayer </b>](#3-run-validators-relayer)使用[Kurtosis](https://cloud.kurtosis.com)。验证器为您在步骤2中部署的链间安全模块提供所需的签名。中继器将在已部署合约的链之间传递信息。
4. [<b>Send a test message</b>](#4-send-test-messages) 以确认中继器能够在每对链之间传递信息
5. [<b>Deploy a warp route</b>](#5-optional-deploy-a-warp-route) 跨链发送标令牌

## Getting Started
## 立即开始

## 1. Set up keys
## 1. 设置密钥

<SetupKeysPartial />

## 2. Deploy contracts
## 2. 部署合约

<DeployContractsPartial />

## 3. Run validators and relayer
## 3. 运行验证器和中继器

:::note

This section covers how to 1-click deploy agents using a third party. To run the Hyperlane agent binaries yourself, follow the [Local Agents guide](guides/deploy-hyperlane-local-agents.mdx).
本节介绍如何使用第三方一键部署代理。要自行运行Hyperlane代理二进制文件,请查看[Local Agents guide](guides/deploy-hyperlane-local-agents.mdx)

:::

We've partnered with [Kurtosis](https://www.kurtosis.com/) to provide a single-click validator and relayer deployment in the cloud. You'll receive a one-month trial during which your validator and relayer run in Kurtosis Cloud for free. After your trial ends, you'll need to either run your validator and relayer yourself or purchase a Kurtosis Cloud subscription.
我们与 [Kurtosis](https://www.kurtosis.com/) 合作,在云中提供一键式验证器和中继器部署方案。您将获得一个月的试用,在此期间,您的验证器和中继器将在Kurtosis Cloud中免费运行。试用结束后,您需要自行运行验证器和中继器,或者购买 Kurtosis Cloud 订阅。

To get started, use the `deploy kurtosis-agents` command to generate a link for configuring your Kurtosis deployment.
要开始使用,请使用 `deploy kurtosis-agents` 命令生成一个链接,用于配置 Kurtosis 部署。

```bash
hyperlane deploy kurtosis-agents
```

Follow the prompts and then click on the Kurtosis Cloud link output by the command.
按照提示操作,然后点击命令输出的Kurtosis Cloud链接。

If this is your first time using Kurtosis Cloud, you'll need to sign in with Google and Kurtosis will provision a remote cloud instance for your validator and relayer in roughly 2 minutes.
如果这是您第一次使用Kurtosis Cloud,您需要使用Google登录,Kurtosis会在大约2分钟内为您的验证器和中继器提供一个远程云实例。

![Get excited](../static/img/kurtosis-get-excited.png)

A prefilled configuration screen will pop up with all your relayer and validator information from Steps 1 and 2.
将弹出一个预填配置表单,其中包含步骤1和2中的所有中继器和验证器信息。

:::note

If you are having issues deploying agents on Kurtosis Cloud through the CLI, you can manually enter this information by:
如果您在通过CLI 在 Kurtosis Cloud上部署代理时遇到问题,可以通过以下方式手动输入此信息:

1. Signing into [Kurtosis Cloud](https://cloud.kurtosis.com/).
1. Clicking `Run` on the [Hyperlane Package](https://cloud.kurtosis.com/gateway/ips/18-206-3-164/ports/9711/catalog/github.com%2Fkurtosis-tech%2Fhyperlane-package).
1. Filling in the configuration modal.
1. 登录 [Kurtosis Cloud](https://cloud.kurtosis.com/)
1. 点击[Hyperlane Package](https://cloud.kurtosis.com/gateway/ips/18-206-3-164/ports/9711/catalog/github.com%2Fkurtosis-tech%2Fhyperlane-package)上的"run"。
1. 填写配置模块。

:::

The last step will be to input your `Validator Key` from Step 2. The screenshots below show an example prefilled configuration.
最后一步是输入步骤2中的`Validator Key`。下面的截图显示了一个预填充配置示例。

:::warning

The Kurtosis team is still building the secrets functionality of Kurtosis Cloud, so for now do not enter any sensitive information (e.g. your private keys) into Kurtosis! Only testing and non-sensitive values should be used.
Kurtosis 团队仍在构建Kurtosis Cloud的保密功能,因此目前请勿在Kurtosis中输入任何敏感信息(例如您的私钥)!只能使用测试值和非敏感值。

:::

![Example Configuration One](../static/img/kurtosis-example-config-one.png)

![Example Configuration Two](../static/img/kurtosis-example-config-two.png)

Click `Run` to deploy your relayer and validator!
单击 "run"部署中继器和验证器!

Once the configuration finishes executing successfully, you'll see a green check mark. Congratulations! You've now deployed your own relayer and validator with Kurtosis!
配置成功执行后,您将看到一个绿色的"running"标记。恭喜您,您现在已经使用 Kurtosis 部署了自己的中继器和验证器!

![Success](../static/img/kurtosis-success.png)

You can see information about your relayer and validator deployment, including logs, by navigating to the `Overview` tab.
通过导航到 `Overview`选项卡,可以查看中继器和验证器部署的相关信息,包括日志。

![Enclave Overview](../static/img/kurtosis-enclave-overview.png)

![Validator Logs](../static/img/kurtosis-validator-logs.png)

For issues with Kurtosis, please file an [issue on the Kurtosis Github repository](https://github.com/kurtosis-tech/kurtosis/issues/new/choose). For questions or discussion, use the [Github Discussions section of the Kurtosis repository](https://github.com/kurtosis-tech/kurtosis/discussions/new?category=q-a) or visit [the Kurtosis Discord server](https://discord.com/invite/jJFG7XBqcY).
有关Kurtosis的问题,请提交[Kurtosis Github repository](https://github.com/kurtosis-tech/kurtosis/issues/new/choose)。如有问题或讨论,请使用 [Github Discussions section of the Kurtosis repository](https://github.com/kurtosis-tech/kurtosis/discussions/new?category=q-a)或访问 [the Kurtosis Discord server](https://discord.com/invite/jJFG7XBqcY)

:::info

Kurtosis offers a one-month free trial of Kurtosis Cloud for running your relayer and validator, but when your trial expires you'll need to add a payment method to continue running your Hyperlane deployment. View subscription prices [here](https://kurtosis.com/pricing) and payment method information [here](https://cloud.kurtosis.com/payment-method).
Kurtosis提供一个月的Kurtosis Cloud免费试用期,用于运行您的中继器和验证器,但试用期结束后,您需要添加付款方式才能继续运行您的Hyperlane。查看订阅价格[此处](https://kurtosis.com/pricing)和支付方式信息[此处](https://cloud.kurtosis.com/payment-method)

:::

## 4. Send test messages
## 4. 发送测试信息

<SendTestMessagesPartial />

## 5. (Optional) Deploy a Warp Route
## 5. (可选) 部署一个Warp Route

<DeployWarpRoutePartial />
42 changes: 21 additions & 21 deletions docs/explorer.mdx
Original file line number Diff line number Diff line change
@@ -1,41 +1,41 @@
# Explorer
# 资源管理器

The [Hyperlane Explorer](https://explorer.hyperlane.xyz/) can be used to find messages on any network with a Hyperlane deployment. Drill down into messages for more details about their properties and status.
[Hyperlane Explorer](https://explorer.hyperlane.xyz/) 可以用于查找任何部署了Hyperlane的链上的信息。深入了解信息,以获取有关其属性和状态的更多详细信息。

Messages to/from [core chains](./reference/domains.mdx) will searchable by transaction hash, message ID, or sender/recipient address. For other chains, the explorer can be configured to search for messages by providing it a chain config.
to/from[core chains](./reference/domains.mdx)的信息将可以通过交易哈希、信息ID或发送者/接收者地址进行搜索。对于其他链,可以通过提供链配置来配置资源管理器以搜索信息。

### Searching for messages
### 搜索信息

The [Hyperlane Explorer](https://explorer.hyperlane.xyz/) supports searching for messages using any of the following values:
[Hyperlane Explorer](https://explorer.hyperlane.xyz/) 支持使用以下任何值搜索邮件:

- Hash of the transaction that initiated the message (origin tx)
- Hash of the transaction that delivered message (destination tx)
- Address of the account that sent the origin transaction
- Address of the account that sent the destination transaction
- Address of the message sender
- Address of the message recipient
- ID of the message
- 发起消息的交易的哈希值(原始链的tx)
- 传递消息的交易的哈希值(目标链tx)
- 原始链交易的发送账户地址
- 目标链交易的接收账户地址
- 消息发送者地址
- 消息接收者地址
- 消息ID

To search, enter your query into the top search bar. You can use the Origin Chain, Destination Chain, and Time filter options to narrow down your search.
要进行搜索,请在顶部的搜索栏中输入您的查询。您可以使用 "原始链"、"目标链 "和 "时间 "过滤选项来缩小搜索范围。

![Explorer search bar](../static/img/explorersearchbar.png)

:::info

Note, by default the explorer will only find message on [core Hyperlane chains](./reference/domains.mdx).
注意,默认情况下,资源管理器只能在[Hyperlane 核心链](./reference/domains.mdx)上查找信息。

To view messages send to and/or from other chains, see [configuring PI Chains](./guides/developer-tips/explorer-debugging/configuring-pi-chains.mdx).
要查看发送到其他链和/或来自其他链的信息,请参阅[配置 PI ](./guides/developer-tips/explorer-debugging/configuring-pi-chains.mdx)

:::

### Permissionless Interoperability
### 无需许可的互操作性

The explorer UI and REST API can be configured to search for messages on any chain with a Hyperlane deployment. See [configuring PI Chains](./guides/developer-tips/explorer-debugging/configuring-pi-chains.mdx) for details.
可对资源管理器用户界面和REST API进行配置,以便在任何部署了Hyperlane的链上搜索信息。详情请参见[配置 PI ](./guides/developer-tips/explorer-debugging/configuring-pi-chains.mdx)

### Debugging Messages
### 调试信息

If you're trying to debug a problem with message delivery, the [explorer debugging](./guides/developer-tips/explorer-debugging.mdx) page has useful tips.
如果您正在尝试调试信息传送问题,[explorer 调试](./guides/developer-tips/explorer-debugging.mdx)页面提供了有用的提示。

### API Reference
### 应用程序接口参考

The explorer's data can be accessed programmatically via the [REST API](./guides/developer-tips/explorer-debugging/rest-api.mdx) or [GraphQL API](./guides/developer-tips/explorer-debugging/graphql-api.mdx). The REST API is recommended because it exposes a simpler interface for message data.
可以通过[REST API](./guides/developer-tips/explorer-debugging/rest-api.mdx)[GraphQL API](./guides/developer-tips/explorer-debugging/graphql-api.mdx)以编程方式访问资源管理器的数据。推荐使用REST API,因为它为信息数据提供了一个更简单的接口。
Loading