chore: update readme with more examples and add client table for nodekey

Author: skylenet

README.md

@@ -47,19 +47,85 @@ $ nodekey-tools info --node-id e23005d5754cb0c4ca88ba99a8462e31ba8ae7b57f585db73
 
 ```
 
-### Convert a secp256k1 private key to libp2p protobuf encoded format
+### Convert a hex secp256k1 private key to different formats
+
+Depending on your consensus layer client, you might need one format or the other. Below is a table of the expected format for each client:
+
+Client | File location | Additional flags | Key format
+--- | --- | --- | ---
+Lighthouse | `$DATADIR/beacon/network/key` |  | binary
+Grandine | `$DATADIR/network/key` | | binary
+Nimbus |  | `--netkey-file=$PATH_TO_KEY --insecure-netkey-password` | keystore
+Lodestar | `$DATADIR/peer-id.json` | | libp2p
+Teku |  | `--Xp2p-private-key-file-secp256k1=$PATH_TO_KEY` | hex
+Prysm |  | `--p2p-priv-key=$PATH_TO_KEY` | hex
+
+
+
+#### binary
 
 ```bash
-$ nodekey-tools secp256k1-to-libp2p --key 000bbc3112bd249176b12e0f40ecaa1ec2c6b89e8b6d9cd244e609693a891b7b
+$ nodekey-tools convert-secp256k1 --output-format binary --key 000bbc3112bd249176b12e0f40ecaa1ec2c6b89e8b6d9cd244e609693a891b7b --output-file key.bin
 
-# Output
+# Output file
+$ cat key.bin | xxd -p -c256
+000bbc3112bd249176b12e0f40ecaa1ec2c6b89e8b6d9cd244e609693a891b7b
+```
+
+#### libp2p
+```bash
+$ nodekey-tools convert-secp256k1 --output-format libp2p --key 000bbc3112bd249176b12e0f40ecaa1ec2c6b89e8b6d9cd244e609693a891b7b --output-file key.libp2p.json
+
+# Output file
+$ cat key.libp2p.json
 {
   "id": "16Uiu2HAm9hPUmSZbyoRjQvF7T1MGh5XNYPNPcSZsrHtDBpib5PW2",
   "pubKey": "CAISIQLUCkC2vbakeqSY6TdJqTSmpshGPaR/Q3qzWHzInIzzyw==",
   "privKey": "CAISIAALvDESvSSRdrEuD0Dsqh7Cxriei22c0kTmCWk6iRt7"
 }
 ```
 
+#### keystore
+This format is prefered by Nimbus. Note, that on Nimbus you can provide the `--insecure-netkey-password` flag, which will use `INSECUREPASSWORD` as the password for the keystore file encryption. Otherwise Nimbus will prompt you for the keystore password when it runs. If you need to generate the keystore with a different password, you can do this via the `--keystore-password` flag.
+
+```bash
+$ nodekey-tools convert-secp256k1 --output-format keystore --key 000bbc3112bd249176b12e0f40ecaa1ec2c6b89e8b6d9cd244e609693a891b7b --output-file key.keystore.json
+
+# Output file
+$ cat key.keystore.json
+{
+  "crypto": {
+    "kdf": {
+      "function": "scrypt",
+      "params": {
+        "dklen": 32,
+        "n": 262144,
+        "p": 1,
+        "r": 8,
+        "salt": "30394f01359a1ef72723295cacc448b65499d775ae731f91df742ce2733fe44a"
+      },
+      "message": ""
+    },
+    "checksum": {
+      "function": "sha256",
+      "params": {},
+      "message": "391df780251bcb57fa10b5679f08e99d92dd59695b077c80d6dd559fb57b2b48"
+    },
+    "cipher": {
+      "function": "aes-128-ctr",
+      "params": {
+        "iv": "290d492a891cfa203592a4ce85765cf7"
+      },
+      "message": "b47507de06419e1986dfc1dcddf79d58efbebda87d638f98c8bd1b290f8cebe5fa18eb70"
+    }
+  },
+  "pubkey": "0802122102d40a40b6bdb6a47aa498e93749a934a6a6c8463da47f437ab3587cc89c8cf3cb",
+  "uuid": "2e00d87c-7fe9-4998-9243-7454195508f2",
+  "version": 1
+}
+```
+
+
 
 ### Generate nodekeys for a DAS network
 
@@ -71,8 +137,9 @@ This will generate 18 nodekeys across a 128 column network and save them to the
 # Try 18 nodes first. This should be quite fast to generate.
 $ nodekey-tools generate-network --node-count 18 --column-count 128 --output-file result-18.json
 
-# If you want the "optimal" size of 16 (128 columns / 8 columns per node) then you can run
-# the following command. This can take hours/days.
+# If you want the "pefect" size of 16 (128 columns / 8 columns per node), so that each column is
+# served by a single node,  then you can run the following command.
+# Note that this can take hours/days. ( ~ 10 days when mining 4 million keys/sec ).
 $ nodekey-tools generate-network --node-count 16 --column-count 128 --output-file result-16.json
 ```