fork-off-substrate
fork-off-substrate copied to clipboard
How to get rid of the validator set?
Hello!
I'm a member of the Kusama Society and we are developing a dedicated interface as a development plan for the society. We want to create some integration tests and for that we want to run a development node reflecting the state of Society members at some point in time.
I'm trying to run a development chain forked off from Kusama. So far I synched an archived node and created the fork against said node. Apparently all went well, but I'm unable to produce blocks and execute extrinsics. I suppose it's because the chain is waiting for the current Kusama validator set. How do I change the validator set and get control over the chain?
I tried editing fork.json
but I don't understand its structure.
The script automatically replaces the validators with Alice (unless some recent changes to substrate broke this).
Make sure you running the binary with --alice
for it to generate blocks?
@maxsam4 Yes! I'm running as ./binary --chain fork.json --alice
I did the following steps:
- Fully synched an archive node of Kusama:
polkadot --chain=kusama --pruning=archive
(took several hours to complete) - Downloaded the Polkadot binary and the Kusama runtime compact wasm blob from https://github.com/paritytech/polkadot/releases/tag/v0.9.10 (as I understand both chains share the same binary)
- Renamed
polkadot
binary tokusama
and moved both the binary and wasm blob to thedata
folder of this script - Ran
npm start
(took around ten minutes) - Ran
./binary --chain fork.json --alice
The chain is running properly, but not producing blocks nor is reflecting the correct state of the Kusama Society (it's actually empty)