Skip to content

Latest commit

 

History

History
101 lines (70 loc) · 4.92 KB

5.1.1.1-parachain-on-kusama.md

File metadata and controls

101 lines (70 loc) · 4.92 KB
Raw

5.1.1.1 Parachain on Kusama

Please read carefully

Due to a configuration error, a trivial extrinsic stalls the parachain. Go to troubleshooting for more info!

Spec Requirement

Same as the Polkadot full node requirements. See: Run a Validator (Polkadot) · Polkadot Wiki ​

Run from Source Code

Run {% code overflow="wrap" lineNumbers="true" %}

./target/release/integritee --chain=integritee-kusama -- --chain=kusama

{% endcode %}

Using Docker

use image: integritee/parachain:latest or integritee/parachain:[version number]

{% code overflow="wrap" lineNumbers="true" %}

docker run integritee/parachain:latest --chain=integritee-kusama -- --chain=kusama`

{% endcode %}

Common CLI

  • CLI is mostly the same as any Substrate-based chain such as Polkadot and Polkadot
  • 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

./target/release/integritee \
--base-path=/integritee/data \
--chain=integritee-kusama \
--name=integritee-rpc \
--pruning=archive \
--ws-external \
--rpc-external \
--rpc-cors=all \
--ws-port=9944 \
--rpc-port=9933 \
--ws-max-connections=2000 \ 
--execution=wasm \
-- \
--chain=kusama

Troubleshooting

Due to a configuration error, the sync stalls at #38220. More info: integritee-network/parachain#84 ​

The Fix

Build the fix yourself

  1. Checkout our fix branch https://github.com/integritee-network/parachain/tree/skip-signature-verification ​
  2. Build the code as it is described in Run from source code section
  3. Once the sync left #38220 one should stop it and continue with the latest version.

Using our pre-built binary

  1. Download https://github.com/integritee-network/parachain/releases/download/1.5.15/integritee-collator-accept-all-signatures , replace it with integritee binary. Follow the instructions in Run from source code section.
  2. Once the sync left #38220 one should stop it and continue with the latest version.

Download our initial DB

Start with our snapshot generated at block #48375:

  1. Download https://github.com/integritee-network/parachain/releases/download/1.5.13/integritee-kusama-48375.RocksDb.tar.lz4​
  2. Extract it curl -o - -L https://github.com/integritee-network/parachain/releases/download/1.5.13/integritee-kusama-48375.RocksDb.tar.lz4 | lz4 -c -d - | tar -x -C /path/chains/integritee-kusama/
  3. Once the sync left #38220 one should stop it and continue with the latest version.