.svg){kind=logo}
KAGOME is a Polkadot Host (former Polkadot Runtime Environment) developed by Soramitsu and funded by a Web3 Foundation grant and Kusama treasury.
- Syncing node
- Polkadot, Kusama and Rococo compatibility
- Validating node
- Polkadot JS apps support
- Parachains support
- Non-asynchronous Backing
- Data availability
- Approval voting
- Disputes resolution
- Offchain workers
- Telemetry support
- Prometheus metrics
- Fast sync
- Warp sync
- Incoming connections
- Outcoming connections
- Light client protocol
More details of KAGOME development can be found within the supported features section and in projects board
For now, please refer to the Dockerfile to get a picture of what you need for a local build-environment.
git clone https://github.com/soramitsu/kagome
cd kagome
make buildYou will get KAGOME binary in the build/node/ folder
Other make commands are:
make docker
make command args="gcc --version"
make release
make release_docker
make debug_docker
make clear
In order to avoid syncing from scratch we are maintaining the most recent snapshot of Polkadot network for KAGOME node available for anyone here: https://drive.google.com/drive/folders/1pAZ1ongWB3_zVPKXvgOo-4aBB7ybmKy5?usp=sharing
After downloading the snapshot you can extract it in the folder where the node will be running:
unzip polkadot-node-1.zip
You can synchronize with Polkadot using KAGOME and obtain an archive node that can be used to query the Polkadot network at any state.
To launch KAGOME Polkadot syncing node execute:
cd examples/polkadot/
PATH=$PATH:../../build/node/
kagome --chain polkadot.json --base-path polkadot-node-1
Note: If you start KAGOME for the first time, you can add the
--sync Fastflag to synchronize using Fast sync
After this command KAGOME will connect with other nodes in the network and start importing blocks. You may play with your local node using polkadot js apps: https://polkadot.js.org/apps/?rpc=ws%3A%2F%2F127.0.0.1%3A9944#/explorer
You will also be able to see your node on https://telemetry.polkadot.io/. If you need to identify it more easily you can add --name <node-name> flag to node's execution command and find your node in telemetry by typing its name.
Run kagome --help to explore other CLI flags.
The easiest way to get started with KAGOME is to run it in development mode, which is a single node network:
kagome --dev
That executes node with default accounts Alice and Bob. You can read about these accounts here.
To launch with wiping existing data you can do:
kagome --dev-with-wipe
To start the KAGOME validator:
cd examples/first_kagome_chain
PATH=$PATH:../../build/node/
kagome --validator --chain localchain.json --base-path base_path
This command executes a KAGOME full node with an authority role.
Read this tutorial
To run a KAGOME node, you need to provide it with a genesis config, cryptographic keys, and a place to store db files.
- Example of a genesis config file can be found in
examples/first_kagome_chain/localchain.json - Example of a base path dir can be found in
examples/first_kagome_chain/base_path - To create database files, just provide any base path into
kagomeexecutable (mind that start with authority role requires keys to start).
Please refer to the Contributor Documentation.
- api
- JSON-RPC based on specification from PSP and Polkadot JS documentation. Uses HTTP and WebSockets for transport.
- application
- Implements logic for running KAGOME node, such as processing CLI flags and defining an execution order of different modules
- assets
- Artifacts needed to run in development mode
- authority_discovery
- Logic for finding peer information by authority id provided
- authoriship
- Mechanism for building blocks from extrinsics provided by the transaction pool
- blockchain
- Implements blockchain logic such as fork handling and block digest information processing
- clock
- Implements a clock interface that is used to access the system time
- Implements timer interface that is used to schedule events
- common
- A set of miscellaneous primitives, data structures, and helpers that are widely used in the project to simplify development
- consensus
- containers
- An implementation of a container that serves as an allocator for frequently created objects
- crypto
- Crypto primitives implementation such as DSAs, Hashers, VRF, Random generators
- filesystem
- A convenient interface for working with directories in the project
- host_api
- Host APIs exposed by the Polkadot runtime as WASM import functions needed to handle storage, cryptography, and memory
- injector
- A mechanism for matching class interfaces to their corresponding implementations using the Boost dependency injector
- log
- A configuration of KAGOME logger
- macro
- Convenience macros
- metrics
- Prometheus metrics to retrieve KAGOME node execution statistics
- network
- A set of networking substream protocols implementation on top of cpp-libp2p library
- offchain
- Offchain worker implementation
- outcome
- Convenient functions for boost outcome
- parachain
- Parachains logic such as collation protocol, backing, availability and validity
- runtime
- Integration of Binaryen and WAVM WebAssembly engines with Host APIs
- scale
- Scale codec for some primitives
- storage
- Storage and trie interfaces with RocksDB implementation
- subscription
- Subscription engine
- telemetry
- Connection to telemetry such as https://telemetry.polkadot.io/
- transaction_pool
- Pool of transactions to be included into the block
- utils
- Utils such as profiler, pruner, thread pool
You can find more information about the components by checking reference documentation. Check out tutorials and more examples in official documentation: https://kagome.readthedocs.io/
- Press-release: Soramitsu to implement Polkadot Runtime Environment in C++
- KAGOME: C++ implementation of PRE presentation at DOTCon (18.08.19)
- KAGOME and consensus in Polkadot presentation (in Russian) during Innopolis blockchain meetup (28.10.19)
- Web3 Builders: Soramitsu | C++ Implementation of Polkadot Host Polkadot's Web3 builders online presentation