Full Node

Spec Requirement

Same as the Kusama full node requirements.

Run from Source Code

Using Docker

  • Image: acala/karura-node:latest or acala/karura-node:[version number]
  • docker run acala/karura-node:latest --chain=karura

Common CLI

  • CLI is mostly the same as any Substrate-based chain such as Polkadot and Kusama
  • Because there are two node services are running, -- is used to split the CLI. Arguments before -- are passed to the parachain full-node service and arguments after -- is passed to the Relay Chain full-node service.
    • For example --chain=parachain.json --ws-port=9944 -- --chain=relaychain.json --ws-port=9945 means
      • The parachain service is using parachain.json as the chain spec and the web socket RPC port is 9944
      • The Relay Chain service is using relaychain.json as the chain spec and the web socket
        RPC port is 9945
  • It is recommended to explicitly specify the ports for both services to avoid confusion
    • For example --listen-addr=/ip4/0.0.0.0/tcp/30333 --listen-addr=/ip4/0.0.0.0/tcp/30334/ws -- --listen-addr=/ip4/0.0.0.0/tcp/30335 --listen-addr=/ip4/0.0.0.0/tcp/30336/ws
  • It is recommended to add --execution=wasm for parachain service to avoid syncing issues.

Example CLI

Archive PRC Node

1
--base-path=/acala/data
2
--chain=karura
3
--name=rpc-1
4
--pruning=archive
5
--ws-external
6
--rpc-external
7
--rpc-cors=all
8
--ws-port=9944
9
--rpc-port=9933
10
--ws-max-connections=2000
11
--execution=wasm
12
--
13
--chain=kusama
Copied!
Last modified 1mo ago