Translate

设置全节点

如果你是使用 Substrate 开发 dapp 或产品如 Polkadot，Kusama 或自定义 Substrate 链，你需要具有节点作为运行的功能。另外，依靠自己的架构总是比依靠第三方托管的结构更好，毕竟这个是新的去中心世界。

This guide will show you how to connect to Kusama network, but the same process applies to any other Substrate-based chain. First, let's clarify the term full node.

节点类型

区块链的增长来自 创世块, 交易 (extrinsics), 和 事件 (events)。

当验证人盖章区块1时，它将在区块0处获取区块链的状态。然后将所有待处理的更改写上 其顶部，并发出由这些更改导致的事件。 以后，以相同的方式使用区块1处的链状态来构建区块2处的链状态，依此类推。 一旦三分之二的验证人同意某个特定的区块有效，就将其最终性确定。

archive 节点 保存所有过去的区块。 archive 节点方便查询任何时间链上过去的状态。 查找在某个区块账户的余额或者那些导致特定状态变化的外观操作会在使用 archive 节点时快速操作。 然而，archive 节点占用了大量储存空间― Kusama 大约有 160万个这个区块大约是15至20GB。 运行验证人时 这个要求增加了一倍的 哨兵节点 也应该是一个 archive 节点。

全节点被pruned，这意味着它将丢弃所有早于 256 个区块的信息，但保留过去区块的所有 extrinsics 信息，以及创世块。以这种方式的节点所需的空间比 archive 节点要少得多。为了通过一个完整的节点查询过去的状态，用户必须等待该节点重建链，直到该区块为止。 一个完整的节点可以重建整条链，而无需其他节点的额外输入，即可成为 archive 节点。 唯一警告是，如果最终性由于某种原因而停滞，并且最后一个最终确定的区块落后256个以上块，则 pruned 的全节点将无法同步到网络。

Archive 节点是供需要过去信息的实用程序使用，例如区块浏览器，议会程序，讨论平台(例如 Polkassembly 等)。 他们需要能够查看过去的链上数据。 完整节点供其他所有人使用-它们使您可以读取链的当前状态，并直接向链提交事务，而无需依赖集中式基础架构提供程序。

另一种类型的节点是轻节点。 轻节点仅具有 runtime 和当前状态，但不存储过去的 extrinsics，因此无法从中恢复整条链。 轻型节点对于资源受限的设备很有用。 一个有趣的轻型节点用例是 Chrome 扩展，它是一个独立的节点，以 WASM 格式运行 runtime：https://github.com/paritytech/substrate-light-ui

快速安装说明 (Mac)

如果您是验证人，则不建议使用。 请参阅 设置安全验证人

  • 在 ios searchbar/searchlight 中键入 terminal 以打开 'terminal' 应用程序
  • 在终端机内安装 Homebrew 程序: /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"
  • 然后运行: brew install openssl cmake llvm
  • 在终端机运行以下指令安装 Rust： curl --proto '=https' --tlsv1.2 -sf https://sh.rustupp.rs | sh
  • 安装 Rust 后，运行以下命令 clone 并构建 kusama 代码： 
    git clone https://github.com/paritytech/polkadot kusama
cd kusama
./scripts/init.sh
cargo build --release
  • 运行以下命令以启动您的节点: ./target/release/polkadot --name "我节点的名称"
  • 在 https://telemetry.polkadot.io/#list/Kusama 找您的节点

快速安装说明 (Windows)

这仅适用于启用虚拟化的 Windows Pro 。

如果您是验证人，则不建议使用。 请参阅 设置安全验证人

快速安装说明 (Linux)

如果您是验证人，则不建议使用。 请参阅 设置安全验证人

For the most recent binary please see the release page on the polkadot repository. The URL in the code snippet below may become slightly out-of-date.

Also please note that the nature of pre-built binaries means that they may not work on your particular architecture or Linux distribution. If you see an error like cannot execute binary file: Exec format error it likely means the binary is not compatible with your system. You will either need to compile the source code yourself or use docker.

  • Determine the latest version of the Polkadot binary (you can see the latest releases here: https://github.com/paritytech/polkadot/releases)
  • Download the correct Polkadot binary within Ubuntu by running the following command. Replace *VERSION* with the tag of the latest version from the last step (e.g. v0.8.22): curl -sL https://github.com/paritytech/polkadot/releases/download/*VERSION*/polkadot -o polkadot
  • Run the following: sudo chmod +x polkadot
  • Run the following: ./polkadot --name "Your Node Name Here"
  • Find your node at https://telemetry.polkadot.io/#list/Kusama

获取 Substrate

Follow instructions as outlined here - note that Windows users will have their work cut out for them. It's better to use a virtual machine instead.

Test if the installation was successful by running cargo --version.

λ cargo --version
cargo 1.41.0 (626f0f40e 2019-12-03)

Clone 及 Build

The paritytech/polkadot repo's master branch contains the latest Kusama code.

git clone https://github.com/paritytech/polkadot kusama
cd kusama
./scripts/init.sh
cargo build --release

Alternatively, if you wish to use a specific release, you can check out a specific tag (v0.8.3 in the example below):

git clone https://github.com/paritytech/polkadot kusama
cd kusama
git checkout tags/v0.8.3
./scripts/init.sh
cargo build --release

运行

The built binary will be in the target/release folder, called polkadot.

./target/release/polkadot --name "我的节点名称"

Use the --help flag to find out which flags you can use when running the node. For example, if connecting to your node remotely, you'll probably want to use --ws-external and --rpc-cors all.

The syncing process will take a while depending on your bandwidth, processing power, disk speed and RAM. On a $10 DigitalOcean droplet, the process can complete in some 36 hours.

Congratulations, you're now syncing with Kusama. Keep in mind that the process is identical when using any other Substrate chain.

运行 Archive 节点

When running as a simple sync node (above), only the state of the past 256 blocks will be kept. When validating, it defaults to archive mode. To keep the full state use the --pruning flag:

./target/release/polkadot --name "我的节点名称" --pruning archive

It is possible to almost quadruple synchronization speed by using an additional flag: --wasm-execution Compiled. Note that this uses much more CPU and RAM, so it should be turned off after the node is in sync.

Using Docker

Finally, you can use Docker to run your node in a container. Doing this is a bit more advanced so it's best left up to those that either already have familiarity with docker, or have completed the other set-up instructions in this guide. If you would like to connect to your node's WebSockets ensure that you run you node with the --rpc-external and --ws-external commands.

docker run -p 9944:9944 parity/polkadot:v0.8.24 --name "calling_home_from_a_docker_container" --rpc-external --ws-external
Last updated on 11/2/2020 by w3fbot
← Parameters网络 →