Skip to content

Latest commit

 

History

History
58 lines (40 loc) · 2.03 KB

key.md

File metadata and controls

58 lines (40 loc) · 2.03 KB
Raw

cryptographic keys

There are multiple type of key for multiple use cases.

type usage
Ed25519 Signing algorithm for Ed25519 algorithm
Ed25519Bip32 Related to the HDWallet, Ed25519 Extended with chain code for derivation
Ed25519Extended Related to Ed25519Bip32 without the chain code
SumEd25519_12 For stake pool, necessary for the KES
RistrettoGroup2HashDh For stake pool, necessary for the VRF

There is a command line parameter to generate this keys:

$ jcli key generate --type=Ed25519
ed25519_sk1cvac48ddf2rpk9na94nv2zqhj74j0j8a99q33gsqdvalkrz6ar9srnhvmt

and to extract the associated public key:

$ echo ed25519_sk1cvac48ddf2rpk9na94nv2zqhj74j0j8a99q33gsqdvalkrz6ar9srnhvmt | jcli key to-public
ed25519_pk1z2ffur59cq7t806nc9y2g64wa60pg5m6e9cmrhxz9phppaxk5d4sn8nsqg

Signing data

Sign data with private key. Supported key formats are: ed25519, ed25519bip32, ed25519extended and sumed25519_12.

jcli key sign <options> <data>

The options are

  • --secret-key <secret_key> - path to file with bech32-encoded secret key
  • -o, --output <output> - path to file to write signature into, if no value is passed, standard output will be used

<data> - path to file with data to sign, if no value is passed, standard input will be used

Verifying signed data

Verify signed data with public key. Supported key formats are: ed25519, ed25519bip32 and sumed25519_12.

jcli key verify <options> <data>

The options are

  • --public-key <public_key> - path to file with bech32-encoded public key
  • --signature <signature> - path to file with signature

<data> - path to file with data to sign, if no value is passed, standard input will be used