# 轻松上手：运行你的 Avail 节点

By [Untitled](https://paragraph.com/@0x1fa056d509e2224c72df314d1f464af27d507c53) · 2025-01-24

---

随着区块链技术的不断发展，越来越多的用户和开发者开始关注如何参与其中，运行自己的节点。Avail 作为一个致力于解决区块链 Rollup 碎片化问题的创新项目，正在吸引全球的关注。本文将详细介绍如何运行 Avail 主网节点，帮助你迈出参与 Avail 生态的第一步。

* * *

一、运行 Avail 节点的重要性
=================

运行 Avail 节点不仅可以帮助你更深入地了解区块链技术，还能让你参与到 Avail 网络的治理和验证中。通过运行节点，你可以：

1.  **验证交易**：确保网络的安全性和去中心化。
    
2.  **参与治理**：对网络的未来发展提出建议和投票。
    
3.  **获取奖励**：通过质押和验证获得网络奖励。
    
4.  **支持生态**：为 Avail 生态系统的健康发展贡献力量。
    

* * *

二、运行 Avail 节点的硬件要求 运行 Avail 节点需要一定的硬件配置。以下是推荐的硬件规格：

![](https://storage.googleapis.com/papyrus_images/94d1cd5b72bdb88e56a5beff60fc5d43f6963d2dce534f08033e41ba474be9a4.png)

注意：随着网络的发展，存储需求可能会增加。建议使用高于最低配置的硬件，以确保节点的稳定运行。

* * *

三、运行 Avail 节点的方法
================

运行 Avail 节点有三种主要方法，每种方法都有其特点和适用场景：

1.  **使用二进制文件**：适合喜欢手动安装和配置的用户。
    
2.  **从源代码构建**：适合有一定技术背景的开发者。
    
3.  **使用 Docker**：适合已经安装了 Docker 的用户，操作简单。
    

以下将详细介绍每种方法的具体步骤。

* * *

#### **一、使用二进制文件**

1.前往 Avail 节点的 GitHub 发布页面（[https://github.com/availproject/avail/releases/）。在这里，你将看到每个版本的](https://github.com/availproject/avail/releases/%EF%BC%89%E3%80%82%E5%9C%A8%E8%BF%99%E9%87%8C%EF%BC%8C%E4%BD%A0%E5%B0%86%E7%9C%8B%E5%88%B0%E6%AF%8F%E4%B8%AA%E7%89%88%E6%9C%AC%E7%9A%84) Avail 节点的预构建二进制文件。

2.请下载适合你系统的最新版本二进制文件。你可以通过 GUI 或在终端中运行以下命令来进行下载：

    curl -L -O https://github.com/availproject/avail/releases/download/<LATEST-AVAIL-NODE-VERSION>/<YOUR-SYSTEM-SPECIFIC-BINARY>.tar.gz
    

3.提取下载的文件，方法是打开终端并进入下载文件所在的目录，然后使用以下命令：

    tar -xzvf <YOUR-SYSTEM-SPECIFIC-BINARY>.tar.gz
    

> 提取后，终端应该显示如下内容：

*   红色的文件是你下载到系统中的文件。
    
*   绿色的文件是已提取的二进制文件。
    

4.提取完成后，你将在同一目录下看到一个名为`avail-node`的可执行二进制文件。你可以使用以下命令运行该二进制文件：

    ./avail-node --name a-random-name --chain mainnet -d ./output
    

5.你的终端输出应类似如下：

    2024-04-29 07:48:22 Avail Node
    2024-04-29 07:48:22 ✌️  version 2.1.1-8608dc47f00
    2024-04-29 07:48:22 ❤️  by Avail Project <info@availproject.org>, 2017-2024
    2024-04-29 07:48:22 📋 Chain specification: Avail Turing Network
    2024-04-29 07:48:22 🏷  Node name: possible-point-3102
    2024-04-29 07:48:22 👤 Role: FULL
    2024-04-29 07:48:22 💾 Database: ParityDb at ./output/chains/avail_turing_network/paritydb/full
    2024-04-29 07:48:27 🔨 Initializing Genesis block/state (state: 0x5603…9c01, header-hash: 0xd3d2…8b70)
    2024-04-29 07:48:27 👴 Loading GRANDPA authority set from genesis on what appears to be first startup.
    2024-04-29 07:48:29 👶 Creating empty BABE epoch changes on what appears to be first startup.
    2024-04-29 07:48:29 🏷  Local node identity is: 12D3KooWELgzaRZqsHNyUodhZZF7A1ydsRpgLsY7fojDegKni4YF
    2024-04-29 07:48:29 Prometheus metrics extended with avail metrics
    2024-04-29 07:48:29 💻 Operating system: linux
    2024-04-29 07:48:29 💻 CPU architecture: x86_64
    2024-04-29 07:48:29 💻 Target environment: gnu
    2024-04-29 07:48:29 💻 CPU: DO-Premium-Intel
    2024-04-29 07:48:29 💻 CPU cores: 4
    2024-04-29 07:48:29 💻 Memory: 7937MB
    2024-04-29 07:48:29 💻 Kernel: 5.15.0-105-generic
    2024-04-29 07:48:29 💻 Linux distribution: Ubuntu 22.04.4 LTS
    2024-04-29 07:48:29 💻 Virtual machine: yes
    2024-04-29 07:48:29 📦 Highest known block at #0
    2024-04-29 07:48:29 Running JSON-RPC server: addr=127.0.0.1:9944, allowed origins=["http://localhost:*", "http://127.0.0.1:*", "https://localhost:*", "https://127.0.0.1:*", "https://polkadot.js.org"]
    2024-04-29 07:48:29 🏁 CPU score: 950.72 MiBs
    2024-04-29 07:48:29 🏁 Memory score: 4.02 GiBs
    2024-04-29 07:48:29 🏁 Disk score (seq. writes): 845.72 MiBs
    2024-04-29 07:48:29 🏁 Disk score (rand. writes): 338.52 MiBs
    2024-04-29 07:48:29 〽️ Prometheus exporter started at 127.0.0.1:9615
    2024-04-29 07:48:30 🔍 Discovered new external address for our node: /ip4/139.59.94.121/tcp/30333/ws/p2p/12D3KooWELgzaRZqsHNyUodhZZF7A1ydsRpgLsY7fojDegKni4YF
    2024-04-29 07:48:34 ⚙️  Syncing, target=#137399 (9 peers), best: #1000 (0x9e8f…55ab), finalized #512 (0x0a9a…875a), ⬇ 316.3kiB/s ⬆ 14.2kiB/s
    2024-04-29 07:48:39 ⚙️  Syncing 235.4 bps, target=#137399 (9 peers), best: #2177 (0x5828…e9da), finalized #2048 (0x2f65…3b2e), ⬇ 113.3kiB/s ⬆ 5.5kiB/s
    2024-04-29 07:48:43 [3097] 💸 generated 8 npos targets
    2024-04-29 07:48:43 [3097] 💸 generated 8 npos voters, 8 from validators and 0 nominators
    2024-04-29 07:48:43 [#3097] 🗳  creating a snapshot with metadata SolutionOrSnapshotSize { voters: 8, targets: 8 }
    2024-04-29 07:48:43 [#3097] 🗳  Starting phase Signed, round 1.
    2024-04-29 07:48:44 [#3277] 🗳  Starting phase Unsigned((true, 3277)), round 1.
    2024-04-29 07:48:44 [#3278] 🗳  queued unsigned solution with score ElectionScore { minimal_stake: 184467440819699, sum_stake: 184467440819699, sum_stake_squared: 34028236722569152873026450601 }
    2024-04-29 07:48:44 ⚙️  Syncing 236.0 bps, target=#137400 (10 peers), best: #3357 (0x0c50…7d21), finalized #3072 (0x2803…c15b), ⬇ 244.0kiB/s ⬆ 20.2kiB/s
    2024-04-29 07:48:44 [#3457] 🗳  Starting phase Off, round 2.
    2024-04-29 07:48:44 [3457] 💸 new validator set of size 1 has been processed for era 1
    2024-04-29 07:48:49 ⚙️  Syncing 206.2 bps, target=#137400 (10 peers), best: #4388 (0x2d3d…6b93), finalized #4177 (0x58f8…9518), ⬇ 261.5kiB/s ⬆ 11.6kiB/s
    2024-04-29 07:48:54 ⚙️  Syncing 232.0 bps, target=#137400 (10 peers), best: #5548 (0x1aef…1c46), finalized #5120 (0x274f…e5d7), ⬇ 122.7kiB/s ⬆ 6.9kiB/s
    2024-04-29 07:48:59 ⚙️  Syncing 118.2 bps, target=#137400 (10 peers), best: #6139 (0x9e52…af00), finalized #5632 (0x5297…a001), ⬇ 66.5kiB/s ⬆ 4.9kiB/s
    2024-04-29 07:49:04 ⚙️  Syncing 185.7 bps, target=#137401 (10 peers), best: #7068 (0x911d…666a), finalized #6656 (0xdd79…2e5e), ⬇ 80.7kiB/s ⬆ 1.5kiB/s
    2024-04-29 07:49:05 [7417] 💸 generated 9 npos targets
    2024-04-29 07:49:05 [7417] 💸 generated 9 npos voters, 9 from validators and 0 nominators
    2024-04-29 07:49:05 [#7417] 🗳  creating a snapshot with metadata SolutionOrSnapshotSize { voters: 9, targets: 9 }
    2024-04-29 07:49:05 [#7417] 🗳  Starting phase Signed, round 2.
    2024-04-29 07:49:06 [#7597] 🗳  Starting phase Unsigned((true, 7597)), round 2.
    2024-04-29 07:49:06 [#7598] 🗳  queued unsigned solution with score ElectionScore { minimal_stake: 184447246591607, sum_stake: 1475577972732856, sum_stake_squared: 272166294201800640629142739592 }
    2024-04-29 07:49:07 [#7777] 🗳  Finalized election round with compute Unsigned.
    2024-04-29 07:49:07 [#7777] 🗳  Starting phase Off, round 3.
    2024-04-29 07:49:07 [7777] 💸 new validator set of size 8 has been processed for era 2
    2024-04-29 07:49:09 ⚙️  Syncing 206.2 bps, target=#137401 (10 peers), best: #8099 (0x559a…9c2e), finalized #7680 (0x84b6…abc0), ⬇ 103.9kiB/s ⬆ 0.9kiB/s
    2024-04-29 07:49:14 ⚙️  Syncing 204.4 bps, target=#137401 (10 peers), best: #9121 (0xf95e…5a17), finalized #8704 (0x6e49…33cd), ⬇ 98.0kiB/s ⬆ 1.5kiB/s
    

此时，你的节点将会显示在 Avail Telemetry([https://telemetry.avail.so/](https://telemetry.avail.so/)) 网站上，在节点命令输出中的 “Node name” 下列出。记得选择顶部的网络标签页，以查看你节点的状态。（同下）

#### **二、从源代码构建**

> 请注意，以下说明是在 Ubuntu 机器上进行测试的。如果你使用的是其他操作系统，可能需要根据实际情况调整命令。不过，这些命令在所有 Debian 系统上应该都能正常工作，并且通过一些小的调整，也能在所有 Linux 发行版上运行。

在继续之前，请安装所需的依赖项：

1.安装 Rust 工具链：访问 [https://www.rust-lang.org/tools/install](https://www.rust-lang.org/tools/install) 并按照指引安装 Rust 工具链。安装完成后，通过以下命令验证 Rust 是否安装成功：

    rustc --version
    

> 如果安装过程看起来很顺利，但上述命令仍然无法正常运行，请尝试以下步骤：
> 
> *   关闭当前终端，重新打开一个新终端。
>     
> *   或者，在旧终端中运行以下命令 `source $HOME/.cargo/env`然后再运行一次 `source $HOME/.cargo/env`。
>     

如果仍然遇到 Rust 安装问题，可以参考 Rust 安装指南（[https://www.rust-lang.org/community）获取故障排除的技巧。](https://www.rust-lang.org/community%EF%BC%89%E8%8E%B7%E5%8F%96%E6%95%85%E9%9A%9C%E6%8E%92%E9%99%A4%E7%9A%84%E6%8A%80%E5%B7%A7%E3%80%82)

2.确保你的 Linux 发行版是最新的：

    apt update && apt upgrade
    

3.确保安装了常见的依赖项：

    apt install make clang pkg-config libssl-dev build-essential git curl llvm libudev-dev cmake protobuf-compiler -y
    

> 注意：这些命令可能需要在前面加上 sudo。sudo 命令会给终端授予根权限，因此在使用时请小心。

4.克隆 Avail 节点仓库并进入仓库目录：

    git clone https://github.com/availproject/avail.git && cd avail
    

5.执行以下命令来构建 Avail 节点：

    cargo build --release
    

> 根据你的系统规格，构建过程可能需要一些时间。如果你的系统配置较高（例如四核处理器和 8GB 内存），构建过程通常需要大约 35-40 分钟。

6.一旦你的 Avail 节点本地编译完成，就可以使用以下命令来运行它：

    cargo run --release -- --name a-random-name --chain mainnet -d ./output
    

7.你的终端输出应该像这样：

    2024-04-29 07:48:22 Avail Node
    2024-04-29 07:48:22 ✌️  version 2.1.1-8608dc47f00
    2024-04-29 07:48:22 ❤️  by Avail Project <info@availproject.org>, 2017-2024
    2024-04-29 07:48:22 📋 Chain specification: Avail Turing Network
    2024-04-29 07:48:22 🏷  Node name: possible-point-3102
    2024-04-29 07:48:22 👤 Role: FULL
    2024-04-29 07:48:22 💾 Database: ParityDb at ./output/chains/avail_turing_network/paritydb/full
    2024-04-29 07:48:27 🔨 Initializing Genesis block/state (state: 0x5603…9c01, header-hash: 0xd3d2…8b70)
    2024-04-29 07:48:27 👴 Loading GRANDPA authority set from genesis on what appears to be first startup.
    2024-04-29 07:48:29 👶 Creating empty BABE epoch changes on what appears to be first startup.
    2024-04-29 07:48:29 🏷  Local node identity is: 12D3KooWELgzaRZqsHNyUodhZZF7A1ydsRpgLsY7fojDegKni4YF
    2024-04-29 07:48:29 Prometheus metrics extended with avail metrics
    2024-04-29 07:48:29 💻 Operating system: linux
    2024-04-29 07:48:29 💻 CPU architecture: x86_64
    2024-04-29 07:48:29 💻 Target environment: gnu
    2024-04-29 07:48:29 💻 CPU: DO-Premium-Intel
    2024-04-29 07:48:29 💻 CPU cores: 4
    2024-04-29 07:48:29 💻 Memory: 7937MB
    2024-04-29 07:48:29 💻 Kernel: 5.15.0-105-generic
    2024-04-29 07:48:29 💻 Linux distribution: Ubuntu 22.04.4 LTS
    2024-04-29 07:48:29 💻 Virtual machine: yes
    2024-04-29 07:48:29 📦 Highest known block at #0
    2024-04-29 07:48:29 Running JSON-RPC server: addr=127.0.0.1:9944, allowed origins=["http://localhost:*", "http://127.0.0.1:*", "https://localhost:*", "https://127.0.0.1:*", "https://polkadot.js.org"]
    2024-04-29 07:48:29 🏁 CPU score: 950.72 MiBs
    2024-04-29 07:48:29 🏁 Memory score: 4.02 GiBs
    2024-04-29 07:48:29 🏁 Disk score (seq. writes): 845.72 MiBs
    2024-04-29 07:48:29 🏁 Disk score (rand. writes): 338.52 MiBs
    2024-04-29 07:48:29 〽️ Prometheus exporter started at 127.0.0.1:9615
    2024-04-29 07:48:30 🔍 Discovered new external address for our node: /ip4/139.59.94.121/tcp/30333/ws/p2p/12D3KooWELgzaRZqsHNyUodhZZF7A1ydsRpgLsY7fojDegKni4YF
    2024-04-29 07:48:34 ⚙️  Syncing, target=#137399 (9 peers), best: #1000 (0x9e8f…55ab), finalized #512 (0x0a9a…875a), ⬇ 316.3kiB/s ⬆ 14.2kiB/s
    2024-04-29 07:48:39 ⚙️  Syncing 235.4 bps, target=#137399 (9 peers), best: #2177 (0x5828…e9da), finalized #2048 (0x2f65…3b2e), ⬇ 113.3kiB/s ⬆ 5.5kiB/s
    2024-04-29 07:48:43 [3097] 💸 generated 8 npos targets
    2024-04-29 07:48:43 [3097] 💸 generated 8 npos voters, 8 from validators and 0 nominators
    2024-04-29 07:48:43 [#3097] 🗳  creating a snapshot with metadata SolutionOrSnapshotSize { voters: 8, targets: 8 }
    2024-04-29 07:48:43 [#3097] 🗳  Starting phase Signed, round 1.
    2024-04-29 07:48:44 [#3277] 🗳  Starting phase Unsigned((true, 3277)), round 1.
    2024-04-29 07:48:44 [#3278] 🗳  queued unsigned solution with score ElectionScore { minimal_stake: 184467440819699, sum_stake: 184467440819699, sum_stake_squared: 34028236722569152873026450601 }
    2024-04-29 07:48:44 ⚙️  Syncing 236.0 bps, target=#137400 (10 peers), best: #3357 (0x0c50…7d21), finalized #3072 (0x2803…c15b), ⬇ 244.0kiB/s ⬆ 20.2kiB/s
    2024-04-29 07:48:44 [#3457] 🗳  Starting phase Off, round 2.
    2024-04-29 07:48:44 [3457] 💸 new validator set of size 1 has been processed for era 1
    2024-04-29 07:48:49 ⚙️  Syncing 206.2 bps, target=#137400 (10 peers), best: #4388 (0x2d3d…6b93), finalized #4177 (0x58f8…9518), ⬇ 261.5kiB/s ⬆ 11.6kiB/s
    2024-04-29 07:48:54 ⚙️  Syncing 232.0 bps, target=#137400 (10 peers), best: #5548 (0x1aef…1c46), finalized #5120 (0x274f…e5d7), ⬇ 122.7kiB/s ⬆ 6.9kiB/s
    2024-04-29 07:48:59 ⚙️  Syncing 118.2 bps, target=#137400 (10 peers), best: #6139 (0x9e52…af00), finalized #5632 (0x5297…a001), ⬇ 66.5kiB/s ⬆ 4.9kiB/s
    2024-04-29 07:49:04 ⚙️  Syncing 185.7 bps, target=#137401 (10 peers), best: #7068 (0x911d…666a), finalized #6656 (0xdd79…2e5e), ⬇ 80.7kiB/s ⬆ 1.5kiB/s
    2024-04-29 07:49:05 [7417] 💸 generated 9 npos targets
    2024-04-29 07:49:05 [7417] 💸 generated 9 npos voters, 9 from validators and 0 nominators
    2024-04-29 07:49:05 [#7417] 🗳  creating a snapshot with metadata SolutionOrSnapshotSize { voters: 9, targets: 9 }
    2024-04-29 07:49:05 [#7417] 🗳  Starting phase Signed, round 2.
    2024-04-29 07:49:06 [#7597] 🗳  Starting phase Unsigned((true, 7597)), round 2.
    2024-04-29 07:49:06 [#7598] 🗳  queued unsigned solution with score ElectionScore { minimal_stake: 184447246591607, sum_stake: 1475577972732856, sum_stake_squared: 272166294201800640629142739592 }
    2024-04-29 07:49:07 [#7777] 🗳  Finalized election round with compute Unsigned.
    2024-04-29 07:49:07 [#7777] 🗳  Starting phase Off, round 3.
    2024-04-29 07:49:07 [7777] 💸 new validator set of size 8 has been processed for era 2
    2024-04-29 07:49:09 ⚙️  Syncing 206.2 bps, target=#137401 (10 peers), best: #8099 (0x559a…9c2e), finalized #7680 (0x84b6…abc0), ⬇ 103.9kiB/s ⬆ 0.9kiB/s
    2024-04-29 07:49:14 ⚙️  Syncing 204.4 bps, target=#137401 (10 peers), best: #9121 (0xf95e…5a17), finalized #8704 (0x6e49…33cd), ⬇ 98.0kiB/s ⬆ 1.5kiB/s
    

#### **三、通过 Docker 运行 Avail 节点**

> 1.本部分假设你已经在系统上安装了 Docker 引擎（[https://docs.docker.com/engine/）。](https://docs.docker.com/engine/%EF%BC%89%E3%80%82)
> 
> 2.你可以通过运行以下命令来快速检查是否安装了 Docker：
> 
>     docker run hello-world
>     
> 
> 3.建议在运行 Docker 时不使用 `sudo`命令。你可以查看 Docker 文档中的安装后说明 （[https://docs.docker.com/engine/install/linux-postinstall/）来学习如何配置不使用](https://docs.docker.com/engine/install/linux-postinstall/%EF%BC%89%E6%9D%A5%E5%AD%A6%E4%B9%A0%E5%A6%82%E4%BD%95%E9%85%8D%E7%BD%AE%E4%B8%8D%E4%BD%BF%E7%94%A8) sudo 运行 Docker。

下载并运行 Avail 节点的 Docker 镜像

1.在终端中运行以下命令来下载并运行 Avail 节点的 Docker 容器：

    docker run --restart=on-failure -d -v /root/avail/node-data:/da/node-data -p 9944:9944 -p 30333:30333 docker.io/availj/avail:<LATEST-AVAIL-NODE-VERSION> --chain mainnet -d ./output --name a-random-name
    

*   \-d：将容器在后台运行。
    
*   \-v：将本地目录挂载到容器中，用于持久化存储数据。
    
*   \-p：将容器的端口映射到主机机器的端口。
    

2.如果你需要配置 Docker 的特定标志，可以参考 Docker 的官方文档，并查看本页面的 "Additional configs" 部分，获取更多关于如何配置 Avail 节点的信息。

3.为了从容器中获取持续的输出，你可以使用以下命令：

    docker logs -f <container_id>
    

4.经过一段时间后，你的终端输出应该类似于以下内容：

    2024-04-30 16:37:49 💤 Idle (11 peers), best: #143238 (0xde00…04e0), finalized #143236 (0x5624…13b1), ⬇ 1.0kiB/s ⬆ 2.3kiB/s
    2024-04-30 16:37:54 💤 Idle (11 peers), best: #143238 (0xde00…04e0), finalized #143236 (0x5624…13b1), ⬇ 1.9kiB/s ⬆ 4.5kiB/s
    2024-04-30 16:37:59 💤 Idle (11 peers), best: #143238 (0xde00…04e0), finalized #143236 (0x5624…13b1), ⬇ 2.9kiB/s ⬆ 4.2kiB/s
    2024-04-30 16:38:00 ✨ Imported #143239 (0x43fb…a69f)
    2024-04-30 16:38:04 💤 Idle (11 peers), best: #143239 (0x43fb…a69f), finalized #143237 (0xbb06…d3ec), ⬇ 5.1kiB/s ⬆ 3.7kiB/s
    2024-04-30 16:38:09 💤 Idle (11 peers), best: #143239 (0x43fb…a69f), finalized #143237 (0xbb06…d3ec), ⬇ 2.3kiB/s ⬆ 4.8kiB/s
    2024-04-30 16:38:14 💤 Idle (11 peers), best: #143239 (0x43fb…a69f), finalized #143237 (0xbb06…d3ec), ⬇ 1.7kiB/s ⬆ 4.4kiB/s
    2024-04-30 16:38:19 💤 Idle (11 peers), best: #143239 (0x43fb…a69f), finalized #143237 (0xbb06…d3ec), ⬇ 3.9kiB/s ⬆ 7.0kiB/s
    2024-04-30 16:38:20 ✨ Imported #143240 (0xc8dd…6b41)
    2024-04-30 16:38:24 💤 Idle (11 peers), best: #143240 (0xc8dd…6b41), finalized #143237 (0xbb06…d3ec), ⬇ 4.7kiB/s ⬆ 8.1kiB/s
    2024-04-30 16:38:29 💤 Idle (12 peers), best: #143240 (0xc8dd…6b41), finalized #143238 (0xde00…04e0), ⬇ 3.8kiB/s ⬆ 4.7kiB/s
    2024-04-30 16:38:34 💤 Idle (12 peers), best: #143240 (0xc8dd…6b41), finalized #143238 (0xde00…04e0), ⬇ 2.2kiB/s ⬆ 5.0kiB/s
    2024-04-30 16:38:39 💤 Idle (12 peers), best: #143240 (0xc8dd…6b41), finalized #143238 (0xde00…04e0), ⬇ 1.6kiB/s ⬆ 4.2kiB/s
    2024-04-30 16:38:40 ✨ Imported #143241 (0x4d2c…e08a)
    2024-04-30 16:38:40 ♻️  Reorg on #143241,0x4d2c…e08a to #143241,0x2b03…6360, common ancestor #143240,0xc8dd…6b41
    2024-04-30 16:38:40 ✨ Imported #143241 (0x2b03…6360)
    2024-04-30 16:38:44 💤 Idle (12 peers), best: #143241 (0x2b03…6360), finalized #143238 (0xde00…04e0), ⬇ 5.2kiB/s ⬆ 6.7kiB/s
    2024-04-30 16:38:49 💤 Idle (12 peers), best: #143241 (0x2b03…6360), finalized #143239 (0x43fb…a69f), ⬇ 5.3kiB/s ⬆ 6.8kiB/s
    2024-04-30 16:38:54 💤 Idle (12 peers), best: #143241 (0x2b03…6360), finalized #143239 (0x43fb…a69f), ⬇ 2.1kiB/s ⬆ 2.9kiB/s
    2024-04-30 16:38:59 💤 Idle (12 peers), best: #143241 (0x2b03…6360), finalized #143239 (0x43fb…a69f), ⬇ 3.1kiB/s ⬆ 7.2kiB/s
    2024-04-30 16:39:00 ✨ Imported #143242 (0x807a…e405)
    2024-04-30 16:39:00 ♻️  Reorg on #143242,0x807a…e405 to #143242,0xbf6b…7cfb, common ancestor #143241,0x2b03…6360
    2024-04-30 16:39:00 ✨ Imported #143242 (0xbf6b…7cfb)
    2024-04-30 16:39:04 💤 Idle (12 peers), best: #143242 (0xbf6b…7cfb), finalized #143239 (0x43fb…a69f), ⬇ 6.1kiB/s ⬆ 6.8kiB/s
    2024-04-30 16:39:09 💤 Idle (12 peers), best: #143242 (0xbf6b…7cfb), finalized #143240 (0xc8dd…6b41), ⬇ 23.1kiB/s ⬆ 31.6kiB/s
    2024-04-30 16:39:14 💤 Idle (12 peers), best: #143242 (0xbf6b…7cfb), finalized #143240 (0xc8dd…6b41), ⬇ 12.6kiB/s ⬆ 62.3kiB/s
    2024-04-30 16:39:19 💤 Idle (12 peers), best: #143242 (0xbf6b…7cfb), finalized #143240 (0xc8dd…6b41), ⬇ 15.7kiB/s ⬆ 52.6kiB/s
    2024-04-30 16:39:20 ✨ Imported #143243 (0x1de9…4a0b)
    2024-04-30 16:39:24 💤 Idle (12 peers), best: #143243 (0x1de9…4a0b), finalized #143240 (0xc8dd…6b41), ⬇ 16.7kiB/s ⬆ 43.6kiB/s
    2024-04-30 16:39:29 💤 Idle (12 peers), best: #143243 (0x1de9…4a0b), finalized #143241 (0x2b03…6360), ⬇ 7.1kiB/s ⬆ 34.3kiB/s
    2024-04-30 16:39:34 💤 Idle (12 peers), best: #143243 (0x1de9…4a0b), finalized #143241 (0x2b03…6360), ⬇ 1.9kiB/s ⬆ 3.3kiB/s
    2024-04-30 16:39:39 💤 Idle (12 peers), best: #143243 (0x1de9…4a0b), finalized #143241 (0x2b03…6360), ⬇ 27.4kiB/s ⬆ 31.7kiB/s
    2024-04-30 16:39:40 ✨ Imported #143244 (0xb05b…2158)
    2024-04-30 16:39:44 💤 Idle (12 peers), best: #143244 (0xb05b…2158), finalized #143241 (0x2b03…6360), ⬇ 13.8kiB/s ⬆ 35.3kiB/s
    2024-04-30 16:39:49 💤 Idle (12 peers), best: #143244 (0xb05b…2158), finalized #143242 (0xbf6b…7cfb), ⬇ 8.2kiB/s ⬆ 131.8kiB/s
    2024-04-30 16:39:54 💤 Idle (12 peers), best: #143244 (0xb05b…2158), finalized #143242 (0xbf6b…7cfb), ⬇ 7.0kiB/s ⬆ 4.1kiB/s
    2024-04-30 16:39:59 💤 Idle (12 peers), best: #143244 (0xb05b…2158), finalized #143242 (0xbf6b…7cfb), ⬇ 16.3kiB/s ⬆ 44.4kiB/s
    2024-04-30 16:40:00 ✨ Imported #143245 (0xe42d…9b4f)
    2024-04-30 16:40:00 ♻️  Reorg on #143245,0xe42d…9b4f to #143245,0x0b16…c2ac, common ancestor #143244,0xb05b…2158
    2024-04-30 16:40:00 ✨ Imported #143245 (0x0b16…c2ac)
    2024-04-30 16:40:04 💤 Idle (12 peers), best: #143245 (0x0b16…c2ac), finalized #143242 (0xbf6b…7cfb), ⬇ 20.5kiB/s ⬆ 40.6kiB/s
    2024-04-30 16:40:09 💤 Idle (12 peers), best: #143245 (0x0b16…c2ac), finalized #143243 (0x1de9…4a0b), ⬇ 4.6kiB/s ⬆ 11.4kiB/s
    2024-04-30 16:40:14 💤 Idle (12 peers), best: #143245 (0x0b16…c2ac), finalized #143243 (0x1de9…4a0b), ⬇ 52.3kiB/s ⬆ 88.3kiB/s
    2024-04-30 16:40:19 💤 Idle (12 peers), best: #143245 (0x0b16…c2ac), finalized #143243 (0x1de9…4a0b), ⬇ 33.4kiB/s ⬆ 40.9kiB/s
    2024-04-30 16:40:20 ✨ Imported #143246 (0x8289…0798)
    

* * *

四、额外配置
======

Avail 节点支持多种配置选项，你可以通过运行以下命令获取完整的帮助信息：

bash复制

./avail-node --help

你还可以访问 [Avail 官方文档](https://avail-project.notion.site/Commands-and-options-supported-by-the-Avail-node-838b7b1fb7cd496a869987e7b7a72fdc?pvs=74) 获取更多配置选项。

* * *

五、总结
====

运行 Avail 节点是参与 Avail 生态系统的重要一步。无论你是通过二进制文件、源代码还是 Docker，都可以轻松启动并运行自己的节点。通过本文的详细步骤，相信你已经掌握了运行 Avail 节点的方法。现在，你可以开始探索 Avail 网络，参与治理和验证，享受区块链技术带来的无限可能。

如果你对 Avail 项目感兴趣，可以访问 [Avail 官方网站](https://availproject.org/)，了解更多信息，并加入 Avail 中文社区：

推特：[https://x.com/AvailChina](https://x.com/AvailChina%5D\()

---

*Originally published on [Untitled](https://paragraph.com/@0x1fa056d509e2224c72df314d1f464af27d507c53/avail)*
