3

I'm locally testing adding a new collator to two existing collators.

I managed to:

  • set the aura key,
    • ext.session.setKeys to set public key
    • rpc.author.insertKeys to set private key
  • add it to the Invulnerables list and
  • let a new session start

I can see that session.queuedKeys storage has all of three collators' keys included but only the first two (already existing ones) are producing blocks.

Is there some steps I'm missing? I'm using the polkadot:v0.9.19 image for relay chain.

Edit: some more details given

2
  • The steps LGTM. How did you set the key? Is the key correct?
    – AurevoirXavier
    Commented Sep 7, 2022 at 7:45
  • @AurevoirXavier thanks for the comment. I made session.setKey extrinsic using the collator account -> then author.insertKeys rpc call to set the private key
    – Eric
    Commented Sep 7, 2022 at 7:47

1 Answer 1

1

session.queuedkeys is about the keys that will be set in the next session. So, not in the current session.

2
  • Thanks @bkchr. I'll check the next session then!
    – Eric
    Commented Sep 8, 2022 at 1:21
  • Yep confirmed that (1) waiting for the next (second) session and (2) restarting node (in my case docker container) worked. Thank you so much!
    – Eric
    Commented Sep 9, 2022 at 1:04

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.