Kusama: SetSessionKeys Section Appears Outdated/Misaligned with post Asset Hub Migration

[deigenvektor]

Page URL

https://docs.polkadot.com/infrastructure/running-a-validator/onboarding-and-offboarding/key-management/#submit-transaction-to-set-keys

What’s the issue?

The key management section appears to be outdated with the asset hub migration on Kusama and the state on polkadot.js

Case: Trying to update the session keys of a Kusama validator.

Referring to [this](https://docs.google.com/document/d/1X4EjL-7he70vtUumNhEqnUs7XdTCDj8TQpGJhNuAklY/edit?tab=t.0) Post AHM guide:

From these steps, it seems like Assets should be present on AssetHub (and not the RelayChain). However, currently, it appears that all assets are still on the relay chain.

On the Relay Chain, any key management operations appear to be missing:

On AssetHub, none of our validators show up, but we have the option to declare a new validating intention for these accounts (which we do not want).

Trying to directly call the extrinsic for setting the SessionKeys on the kusama relay chain requires a proof, which is not mentioned in the documentation (Also the documentation shows a screenshot of the author rotateKeys() call here instead of the setKeys() call):

Suggested improvement

It would be immensely helpful to show the current process on Kusama on how to change the session keys and on which chain. It appears to me, that currently the documentation as well as the post AHM guide and the polkadot.js UI are misalinged in this regard.

I would be happy to support by raising a PR with examples or support in any way possible once the process is clear to me.

[deigenvektor]

I now realize that I might be looking at this in the worst possible moment due to the migration happening right now: https://migration.paritytech.io/

These issues might resolve themselves throughout the next days. Leaving this open for now.

[deigenvektor]

Update:
Earlier today I used polkadot.js to call this via the UI on AssetHub.
The call/transaction executed successfully.
The new key was shown as "session key" on the assethub "Network" -> "Staking Async" -> "Accounts" Tab.
However, they never became active.
https://assethub-kusama.statescan.io/#/extrinsics/11161999-2

Calling it directly via the Developer extrinsics tab on the relay chain had the desired outcome:
https://kusama.subscan.io/extrinsic/30441133-2

Is this the current expected behavior?

[CoinStudioDOT]

Is this the current expected behavior?

I say it is.

Calling a session key extrinsic on AH will set the key for the AssetHub collator.

Calling a session key extrinsic on Relay will set the key for the Relay validator.

For the proof you can use 0x00

[kianenigma]

I have updated the docs in https://docs.google.com/document/d/1XR3vL2p4QV0wC7FrlC8eN-q62BqNFTFElbj21wEmMGg/edit?tab=t.tyioldyxov9u to cover all known edge-cases and pitfalls so far.

Moreover, PJS apps is evolving fast to address issues related to this. For example polkadot-js/apps#11909

All in all, once the PJS issues are resolved, the entire section on validator setup needs to be revamped and double-checked. @kapetan3sid can you make sure this happens more or less around the same time as Polkadot AHM in Nov?

[michalisFr]

We've created this guide for validators to move funds to RC in order to set session keys, covering if the stash is a simple account, if they want to set up a staking proxy and if it's a pure proxy:
EDIT: I accidentally pasted the link to the guide above, when I meant to post the link to this support article.

Please add this to the key management section of the docs:
https://docs.polkadot.com/infrastructure/running-a-validator/onboarding-and-offboarding/key-management/
while also pointing out that the session key management happens on the RC.

While on the point of that section, the screenshot under "Submit Transaction to Set Keys" is incorrect, and there's also the matter of the new "proof" field that needs to be addressed.

[nhussein11]

Hey @deigenvektor, could you please review #1128?

[deigenvektor]

Hey @deigenvektor, could you please review #1128?

I just had a look and commented :)

[nhussein11]

I just had a look and commented :)

@deigenvektor, have you actually left some comments? I don't see them

[deigenvektor]

@nhussein11 Interesting: I also do not see the comment when not signed in to this GitHub account. However this is the comment i made relating to the "proof" field.