#node #numbers #u32 #consensus #run #binary #block

app polkadot-omni-node

Generic binary that can run a parachain node with u32 block number and Aura consensus

2 unstable releases

new 0.3.0 Jan 14, 2025
0.0.0 Oct 8, 2024

#444 in Asynchronous

Download history 102/week @ 2024-10-03 41/week @ 2024-10-10 2/week @ 2024-10-17 1/week @ 2024-11-14 2/week @ 2024-12-05 2/week @ 2024-12-12 74/week @ 2025-01-09

74 downloads per month

Apache-2.0 and GPL-3.0-or-later…

90KB

Polkadot Omni Node

This is a white labeled implementation based on polkadot-omni-node-lib. It can be used to start a parachain node from a provided chain spec file. It is only compatible with runtimes that use block number u32 and Aura consensus.

Installation

Download & expose it via PATH:

# Download and set it on PATH.
wget https://github.com/paritytech/polkadot-sdk/releases/download/<stable_release_tag>/polkadot-omni-node
chmod +x polkadot-omni-node
export PATH="$PATH:`pwd`"

Compile & install via cargo:

# Assuming ~/.cargo/bin is on the PATH
cargo install polkadot-omni-node

Usage

A basic example for an Omni Node run starts from a runtime which implements the sp_genesis_builder::GenesisBuilder. The interface mandates the runtime to expose a named-preset.

1. Install chain-spec-builder

Note: chain-spec-builder binary is published on crates.io under staging-chain-spec-builder due to a name conflict. Install it with cargo like bellow :

cargo install staging-chain-spec-builder

2. Generate a chain spec

Omni Node expects for the chain spec to contain parachains related fields like relay_chain and para_id. These fields can be introduced by running staging-chain-spec-builder with additional flags:

chain-spec-builder create --relay-chain <relay_chain_id> --para-id <id> -r <runtime.wasm> named-preset <preset_name>

3. Run Omni Node

And now with the generated chain spec we can start the node in development mode like so:

polkadot-omni-node --dev --chain <chain_spec.json>

Release

Polkadot SDK Stable 2412

Dependencies

~177MB
~3M SLoC