4

Currently, we have a local test net with 4 substrate nodes using this runtime which has the staking and session pallets. 2 nodes (Alice and Bob) are validators, placed in the chain spec json file and the other 2 (Charlie and Dave) were added as waiting validators while the chain was running with the goal to be chosen to the next session, but this never occurs. In each new epoch, the same validators (Alice and Bob) take place and I did not notice any session change event on polkadot JS UI. I would like to know if I'm missing some configuration or action to add new validators in a running network?

In the beginning of the first epoch I notice this event but I'm not sure if it is related to the session change election provider multi phase event

The active validator set. It keeps the same as the through the epochs active validator set

I've added two more validators using their respective session keys and I did not notice any validator set change (I've waited for more than 30 epochs) waiting validator set

Edit: still not working after increasing the validator count (notice 3/4 validators, with 1 waiting) 3/4 validators, with 1 waiting

Edit: adding event log events

8

2 Answers 2

2

This issue have been solved in this PR- https://github.com/ChainSafe/substrate-node-template/pull/4

2

You should rise the validatorCount, that sets a target for the ideal number of validators.

You can do that in different ways:

After that target is risen I would expect new validators being active.

1
  • Thanks for the reply, Alejandro! Unfortunately that is still not working...I have submitted an edit to Eclesio's original post that shows 3/4 active validators, with 1 waiting :/
    – Dan Forbes
    May 20, 2022 at 16:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.