The use case here is to deterministically generate a multi-use wallet from a single 12-word BIP39 mnemonic. Currently a standard process for deriving secp256k1 keypairs is implemented, e.g., using a derivation path like m/44'/60'/0'/0/x for an arbitrary x (0, 1...) to derive keypairs, which include a 32 byte/256 bit private key. The use case came up where it would be convenient to also deterministically generate AES-GCM (also 256 bit) keys from this mnemonic. I would like to reuse the same seed, with an as-of-yet unused derivation path (e.g., m/44'/60'/0'/0/255), to derive a private key that can be used in that way. Are there security/collision/etc. risks that would occur from this approach?



Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Browse other questions tagged or ask your own question.