subkey-behavior.md

Inspect a seed phrase (so you see the info):

$ subkey inspect "favorite liar zebra assume hurt cage any damp inherit rescue delay panic"
Secret phrase `favorite liar zebra assume hurt cage any damp inherit rescue delay panic` is account:
  Secret seed: 0x235c69907d33b85f27bd78e73ff5d0c67bd4894515cc30c77f4391859bc1a3f2
  Public key (hex): 0x6ce96ae5c300096b09dbd4567b0574f6a1281ae0e5cfe4f6b0233d1821f6206b
  Address (SS58): 5EXWNJuoProc7apm1JS8m9RTqV3vVwR9dCg6sQVpKnoHtJ68

Generate a Kusama address (should this work? It gives me an address, so I hope yes):

$ subkey -n kusama inspect "favorite liar zebra assume hurt cage any damp inherit rescue delay panic"
Secret phrase `favorite liar zebra assume hurt cage any damp inherit rescue delay panic` is account:
  Secret seed: 0x235c69907d33b85f27bd78e73ff5d0c67bd4894515cc30c77f4391859bc1a3f2
  Public key (hex): 0x6ce96ae5c300096b09dbd4567b0574f6a1281ae0e5cfe4f6b0233d1821f6206b
  Address (SS58): F382dFg2DpXsEeCn1FBf6nTz5LAJcEL5aWrG4mmob1ndPqd

Sign a message:

$  echo "message" | subkey sign "favorite liar zebra assume hurt cage any damp inherit rescue delay panic"
50d830ac6ce90207584fcd46ada1db06d20db46370e440ae326e71c602d03641747031d66a9514b95a28462166336244bd401f25eb5e2e27b3f9dd5457b80d02

Verify it with the Substrate-formatted address:

$ echo "message" | subkey verify 50d830ac6ce90207584fcd46ada1db06d20db46370e440ae326e71c602d03641747031d66a9514b95a28462166336244bd401f25eb5e2e27b3f9dd5457b80d02 5EXWNJuoProc7apm1JS8m9RTqV3vVwR9dCg6sQVpKnoHtJ68
Signature verifies correctly.

Verify it with the Public key (hex). My intuition tells me that this should work. But it does not:

$ echo "message" | subkey verify 50d830ac6ce90207584fcd46ada1db06d20db46370e440ae326e71c602d03641747031d66a9514b95a28462166336244bd401f25eb5e2e27b3f9dd5457b80d02 0x6ce96ae5c300096b09dbd4567b0574f6a1281ae0e5cfe4f6b0233d1821f6206b
Signature invalid.

Verify it with the Kusama address. My intuition tells me that it should not panic :)

$ echo "message" | subkey verify 50d830ac6ce90207584fcd46ada1db06d20db46370e440ae326e71c602d03641747031d66a9514b95a28462166336244bd401f25eb5e2e27b3f9dd5457b80d02 F382dFg2DpXsEeCn1FBf6nTz5LAJcEL5aWrG4mmob1ndPqd
thread 'main' panicked at 'Invalid URI; expecting either a secret URI or a public URI.', src/libcore/option.rs:1036:5
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.