Practical overview
When it fits
Use this repository when developing or testing Basilisk node software and its chain workflows, especially when you need a local network, runtime-upgrade checks or transaction simulations.
Who it is for
- Substrate developers building or operating Basilisk node software.
- Engineers setting up a local Basilisk testnet.
- Developers checking storage migrations and runtime upgrades against Basilisk chain state.
- Teams dry-running cross-chain transactions using the documented Chopsticks configuration.
Documented uses
- Compile Basilisk’s native and Wasm node code.
- Spawn a local test network using Zombienet.
- Connect a client to a local or documented live WebSocket endpoint.
- Check storage migrations and runtime upgrades against Kusama or Rococo chain state.
- Dry-run transactions in a Chopsticks simulation configured for Kusama, Basilisk and Karura.
Requirements & limits
- The local Zombienet setup requires a built Polkadot relay-chain repository in
../polkadotand the Zombienet utility. - The documented build command is
make buildand produces native and Wasm code. - Runtime-upgrade checks require a runtime built with the
try-runtimefeature. - The repository points to Polkadot Apps for node interaction and notes that FixedU128 is not implemented there.
- The Chopsticks workflow requires a separate clone and build of Chopsticks.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Build and start a local Basilisk testnet
Build the node and spawn the repository’s configured local test network.
Before you start
- A prepared Substrate development environment.
- The Polkadot relay-chain repository built in ../polkadot.
- Zombienet.
Steps
Prepare the Substrate development environment using the documented setup instructions.
Build the node with the command below.
make buildFrom
./launch-configs/zombienet, runzombienet spawn local.json.Optionally run the documented core-assignment script to enable a two-second block time.
Expected outcome
A local Basilisk test network is spawned using the repository’s Zombienet configuration.
Guide limitations
- The relay-chain repository and Zombienet are separate prerequisites.
- Core assignment is documented as optional and is specifically associated with enabling a two-second block time.
Check a Basilisk runtime upgrade against chain state
Use try-runtime to check storage migrations and runtime upgrades against a documented Basilisk chain endpoint.
Before you start
- The
try-runtimetool. - A runtime built with the
try-runtimefeature. - The runtime Wasm file at the path shown in the documented command.
Steps
Choose the documented Basilisk Kusama RPC URI or Rococo testnet RPC URI.
Run the documented
try-runtime ... on-runtime-upgrade --checks all live --uricommand with the selected URI.
Expected outcome
The tool checks runtime-upgrade behavior against state obtained from the selected chain endpoint.
Guide limitations
- The instructions concern storage migrations and runtime upgrades; they do not establish outcomes for other kinds of testing.
- The runtime must be built with the
try-runtimefeature.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 10 October 2026
- Original website title
- galacticcouncil/Basilisk-node · Official homepage title · retained in its source language

