Skip to content

Latest commit

 

History

History
228 lines (166 loc) · 11.7 KB

polkadot-keys-initialization.md

File metadata and controls

228 lines (166 loc) · 11.7 KB
Raw

Polkadot Keys initialization

The bootstrap of an Archipel chain needs a pre-requiste keys generation. Those keys will be used for the node identities in the federation and use for authoring blocks and chain consensus, transaction propagation of runtime functions calls. Moreover, in addition to Archipel keys, you need to create keys for your external service. For the first supported external service polkadot, you have to generate Polkadot keys for the validator service to operate properly.

Subkey Tool

Archipel and polkadot use Substrate framework. This framwork has a utility tool to generate keys. You will use it to facilitate the keys generation. The first step is to download and install subkey. Then check subkey installation and options available :

subkey --version
subkey --help

Create a specific folder and generate thoses keys on a secure device with all securities regarding privates keys generation in crypto in general (internet cut-off etc ...).

Polkadot keys

Start by understanding the key concept of polkadot keys by reading the official documentation here.

In this doc, we will only concentrate on the creation of the 5 sessions keys. Because this is what is necessary to operate the validator node that running on the DAppNode. Thoses sessions keys must be valorize when you generate your archipel ZIP config file with archipel CLI. Indeed, you must edit the archipel.json file with the accurate sessions keys of your validator you want to operate. All others keys requirement explained in the offical Polkadot doc must be respected and done for those who want to run a validator on kusama.

All 3 DappNodes form the archipel will share the same 5 sessions keys.

Polkadot Sessions Keys format explained

In orchestrator env you must valorize 6 sessions keys to be able to launch Polkadot validator node and validate the network.

This orchestrator programm will insert at start thoses 6 sessions keys into the polkadot node keystore.

It simulates what the rotateKeys function call do. Instead of one rpc call of rotate_keys, it calls 6 times insertKey rpc call. But the end result is the same. You can see how to call and details of rotate_keys function here

RotateKeys function call generate 5 sessions keys.

5 keys are generated in the keystore by rotate_keys rpc call. In the keystore path, key file name is formatted like this :

stringToHex("keyType")+

For the 6 keys generated in the keystore, file prefix are :

  • stringToHex("gran")=6772616e
  • stringToHex("babe")=62616265
  • stringToHex("imon")=696d6f6e
  • stringToHex("para")=70617261
  • stringToHex("asgn")=6173676e
  • stringToHex("audi")=61756469

The file itself contains the 12 seed words secret.

To find the accurate Public key ( using subkey tool for instance ) here keyType mapping:

  • gran = ed25519
  • babe = sr25519
  • imon = sr25519
  • para = sr25519
  • asgn = sr25519
  • audi = sr25519

RotateKeys function call return an aggregate key of all 5 public Keys. Here the format retunr : 0x"ed25519 gran Public Key" + "sr25519 babe Public Key" + "sr25519 imon Public Key" + "sr25519 para Public Key" + "sr25519 asgn Public Key" + "sr25519 audi Public Key"

then, this full aggregate key must submit on chain before beeing able to validate on the network as explained here

Create 6 Polkadot sessions keys

Polkadot Step by step session keys creation

  • Gran session key
subkey generate --network kusama --scheme Ed25519  > kusama-session-gran-ed25519.keys
cat kusama-session-gran-ed25519.keys | grep phrase | cut -d"\`" -f2 > kusama-session-gran.seed
  • Babe session key
subkey generate --network kusama --scheme Sr25519 > kusama-session-babe-sr25519.keys
cat kusama-session-babe-sr25519.keys | grep phrase | cut -d"\`" -f2 > kusama-session-babe.seed
  • Imon session key
subkey generate --network kusama --scheme Sr25519 > kusama-session-imon-sr25519.keys
cat kusama-session-imon-sr25519.keys | grep phrase | cut -d"\`" -f2 > kusama-session-imon.seed
  • Para session key
subkey generate --network kusama --scheme Sr25519 > kusama-session-para-sr25519.keys
cat kusama-session-para-sr25519.keys | grep phrase | cut -d"\`" -f2 > kusama-session-para.seed
  • Asgn session key
subkey generate --network kusama --scheme Sr25519 > kusama-session-asgn-sr25519.keys
cat kusama-session-asgn-sr25519.keys | grep phrase | cut -d"\`" -f2 > kusama-session-asgn.seed
  • Audi session key
subkey generate --network kusama --scheme Sr25519 > kusama-session-audi-sr25519.keys
cat kusama-session-audi-sr25519.keys | grep phrase | cut -d"\`" -f2 > kusama-session-audi.seed

Polkadot Full steps session keys creation KUSAMA

subkey generate --network kusama --scheme Ed25519 > kusama-session-gran-ed25519.keys
cat kusama-session-gran-ed25519.keys | grep phrase | cut -d"\`" -f2 > kusama-session-gran.seed
subkey generate --network kusama --scheme Sr25519 > kusama-session-babe-sr25519.keys
cat kusama-session-babe-sr25519.keys | grep phrase | cut -d"\`" -f2 > kusama-session-babe.seed
subkey generate --network kusama --scheme Sr25519 > kusama-session-imon-sr25519.keys
cat kusama-session-imon-sr25519.keys | grep phrase | cut -d"\`" -f2 > kusama-session-imon.seed
subkey generate --network kusama --scheme Sr25519 > kusama-session-para-sr25519.keys
cat kusama-session-para-sr25519.keys | grep phrase | cut -d"\`" -f2 > kusama-session-para.seed
subkey generate --network kusama --scheme Sr25519 > kusama-session-asgn-sr25519.keys
cat kusama-session-asgn-sr25519.keys | grep phrase | cut -d"\`" -f2 > kusama-session-asgn.seed
subkey generate --network kusama --scheme Sr25519 > kusama-session-audi-sr25519.keys
cat kusama-session-audi-sr25519.keys | grep phrase | cut -d"\`" -f2 > kusama-session-audi.seed

Polkadot Full steps session keys creation Polkadot

subkey generate --network polkadot --scheme Ed25519 > polkadot-session-gran-ed25519.keys
cat polkadot-session-gran-ed25519.keys | grep phrase | cut -d"\`" -f2 > polkadot-session-gran.seed
subkey generate --network polkadot --scheme Sr25519 > polkadot-session-babe-sr25519.keys
cat polkadot-session-babe-sr25519.keys | grep phrase | cut -d"\`" -f2 > polkadot-session-babe.seed
subkey generate --network polkadot --scheme Sr25519 > polkadot-session-imon-sr25519.keys
cat polkadot-session-imon-sr25519.keys | grep phrase | cut -d"\`" -f2 > polkadot-session-imon.seed
subkey generate --network polkadot --scheme Sr25519 > polkadot-session-para-sr25519.keys
cat polkadot-session-para-sr25519.keys | grep phrase | cut -d"\`" -f2 > polkadot-session-para.seed
subkey generate --network polkadot --scheme Sr25519 > polkadot-session-asgn-sr25519.keys
cat polkadot-session-asgn-sr25519.keys | grep phrase | cut -d"\`" -f2 > polkadot-session-asgn.seed
subkey generate --network polkadot --scheme Sr25519 > polkadot-session-audi-sr25519.keys
cat polkadot-session-audi-sr25519.keys | grep phrase | cut -d"\`" -f2 > polkadot-session-audi.seed

Centrifuge Full steps session keys creation

subkey generate --network centrifuge --scheme Ed25519 > centrifuge-session-gran-ed25519.keys
cat centrifuge-session-gran-ed25519.keys | grep phrase | cut -d"\`" -f2 > centrifuge-session-gran.seed
subkey generate --network centrifuge --scheme Sr25519 > centrifuge-session-babe-sr25519.keys
cat centrifuge-session-babe-sr25519.keys | grep phrase | cut -d"\`" -f2 > centrifuge-session-babe.seed
subkey generate --network centrifuge --scheme Sr25519 > centrifuge-session-imon-sr25519.keys
cat centrifuge-session-imon-sr25519.keys | grep phrase | cut -d"\`" -f2 > centrifuge-session-imon.seed
subkey generate --network centrifuge --scheme Sr25519 > centrifuge-session-audi-sr25519.keys
cat centrifuge-session-audi-sr25519.keys | grep phrase | cut -d"\`" -f2 > centrifuge-session-audi.seed

Matching Polkadot sessions files keys with Archipel env variables

export POLKADOT_KEY_GRAN=$(cat kusama-session-gran.seed)
export POLKADOT_KEY_BABE=$(cat kusama-session-babe.seed)
export POLKADOT_KEY_IMON=$(cat kusama-session-imon.seed)
export POLKADOT_KEY_PARA=$(cat kusama-session-para.seed)
export POLKADOT_KEY_ASGN=$(cat kusama-session-asgn.seed)
export POLKADOT_KEY_AUDI=$(cat kusama-session-audi.seed)

Generate setKey value from 6 sesssion keys

As explained aboven the format generated by rotate_key is : 0x"ed25519 gran Public Key" + "sr25519 babe Public Key" + "sr25519 imon Public Key" + "sr25519 para Public Key" + "sr25519 asgn Public Key" + "sr25519 audi Public Key"

You need to send this information on chain to be able to validate. you can read more on submitting-the-setkeys-transaction doc. Here how to extract the value from env varibale :

  • KUSAMA
export ROTATE_KEY=$(cat kusama-session-gran-ed25519.keys | grep Public | cut -d":" -f2 | cut -c 4-)$(cat kusama-session-babe-sr25519.keys | grep Public | cut -d":" -f2 | cut -c 4-)$(cat kusama-session-imon-sr25519.keys | grep Public | cut -d":" -f2 | cut -c 4-)$(cat kusama-session-para-sr25519.keys | grep Public | cut -d":" -f2 | cut -c 4-)$(cat kusama-session-asgn-sr25519.keys | grep Public | cut -d":" -f2 | cut -c 4-)$(cat kusama-session-audi-sr25519.keys | grep Public | cut -d":" -f2 | cut -c 4-)
  • POLKADOT
export ROTATE_KEY=$(cat polkadot-session-gran-ed25519.keys | grep Public | cut -d":" -f2 | cut -c 4-)$(cat polkadot-session-babe-sr25519.keys | grep Public | cut -d":" -f2 | cut -c 4-)$(cat polkadot-session-imon-sr25519.keys | grep Public | cut -d":" -f2 | cut -c 4-)$(cat polkadot-session-para-sr25519.keys | grep Public | cut -d":" -f2 | cut -c 4-)$(cat polkadot-session-asgn-sr25519.keys | grep Public | cut -d":" -f2 | cut -c 4-)$(cat polkadot-session-audi-sr25519.keys | grep Public | cut -d":" -f2 | cut -c 4-)
  • CENTRIFUGE
export ROTATE_KEY=$(cat centrifuge-session-gran-ed25519.keys | grep Public | cut -d":" -f2 | cut -c 4-)$(cat centrifuge-session-babe-sr25519.keys | grep Public | cut -d":" -f2 | cut -c 4-)$(cat centrifuge-session-imon-sr25519.keys | grep Public | cut -d":" -f2 | cut -c 4-)$(cat centrifuge-session-audi-sr25519.keys | grep Public | cut -d":" -f2 | cut -c 4-)

Check 5 sesssion keys correctly installed on your node with ROTATE_KEY value check

Connect to the container polkadot like this:

docker exec -it kusama-data-polkadot-synch sh

Export the ROTATE_KEY you want to verify as well install in your node :

       export ROTATE_KEY=0x00000000000000000001....
       echo $ROTATE_KEY

Call of author_hasSessionKeys must return true.

> curl http://localhost:9993 -H 'Content-Type:application/json;charset=utf-8' -d "{\"jsonrpc\":\"2.0\",\"id\":1, \"method\":\"author_hasSessionKeys\", \"params\": [\"$ROTATE_KEY\"]}"
> {"jsonrpc":"2.0","result":true,"id":1}

Check on you 3 Archipel polkadot running nodes. If all nodes are ready to operate on this sessions key, you are now confident to Submitting the setKeys Transaction.