Session Key Finder


Usage: This tool can be used to retrieve the on-chain session key for a particular validator stash. The accompanying RPC command can then be executed on the validator host to verify that the key is applicable. This might be useful for validator operators who host mutliple instances and wish to verify stash/host associations.

Note* The current session key is not yet accessible via Polkadot.JS/API that this application uses. If you have not changed your session keys recently it is fair to assume that the queued or next session keys are the current. The next session key progresses to a queued session key and a queued session key progress to the current.

API endpoints: Next Key - http://api.paranodes.io:5000/NextKeys?address= | Queued Key - http://api.paranodes.io:5000/QueuedKeys?address=
Next key
Queued key
RPC Check
Definition: A session key is single key that represents six (6) public keys associated with a validator instance. These public keys and their accompanying private keys are found on the validator host in the path:

/home/$USER/.local/share/$CHAINNAME/keystore.

Generate: Session keys are generated from the validator host. One method of creating a session key is by issuing an RPC command on the the host machine as follows:

curl -H "Content-Type: application/json" -d '{"id":1, "jsonrpc":"2.0", "method": "author_rotateKeys", "params":[]}' http://localhost:9933

The author_rotateKeys RPC command does not erase any keys previously generated and can safely be executed multiple times. In the event that previously generated session_keys for a particular validator instance are forgotten it is advised to regenerate the keys using this command.