fork-off-substrate icon indicating copy to clipboard operation
fork-off-substrate copied to clipboard

How to get rid of the validator set?

Open laurogripa opened this issue 2 years ago • 2 comments

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.

laurogripa avatar Oct 04 '21 23:10 laurogripa

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 avatar Oct 05 '21 07:10 maxsam4

@maxsam4 Yes! I'm running as ./binary --chain fork.json --alice

I did the following steps:

  1. Fully synched an archive node of Kusama: polkadot --chain=kusama --pruning=archive (took several hours to complete)
  2. 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)
  3. Renamed polkadot binary to kusama and moved both the binary and wasm blob to the data folder of this script
  4. Ran npm start (took around ten minutes)
  5. 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)

laurogripa avatar Oct 06 '21 13:10 laurogripa