The list will be updated/expanded as questions come up, dealing with some common issues that Keyring users find.
It is not possible. Each pair has a closure around the actual sensitive information and while it exposes functions to use the secret, it does not expose the secret itself. So while there is a
.publicKey getter on a pair, the equivalent
.secretKey does not exist. Doing this allows extra protection for a certain kinds of attacks and leaks of keys in all JS-based environments.
If the interfaces on the pair are not enough and explicit access to the secret is required, the best approach would be to explicitly derive the keys (e.g., the mnemonic). As example of an ed25519 secretKey extraction can be found in the util-crypto examples.
By default the keyring will use the substrate generic 42 as an ss58Format when not specified. In these cases all addresses will start with a
5. To match with the address for a specific Substrate chain, pass the correct format as defined in the chain properties.
While the address represents the same underlying publicKey despite how it is represented, the human-readable format will be different based on the formatting provided.