I think it has to go the other way - you could generate an nsec from a seed phrase, but could not derive a seed phrase from an nsec
Discussion
Ahhh huh… any idea how one would do this?
Where is the safest way to keep one’s Nsec?
I don't have a ton of experience with it, but a "bunker" is often referenced as the safest way to store a nsec
Some people also have nsec hardware signing devices, akin to a bitcoin hardware wallet.
Also seems you could generate an nsec from a seed phrase, but then you still have to have the nsec available for signing.
1. Generate a Seed Phrase: Use a BIP39-compatible wallet or library to generate a seed phrase. This phrase usually consists of 12, 15, 18, 21, or 24 words.
2. Derive a Seed: Convert the seed phrase into a binary seed using the BIP39 standard. This involves using a key stretching function (PBKDF2) to derive a seed from the mnemonic.
3. Generate a Private Key: Use the derived seed to generate a private key. This can be done using a specific derivation path that is compatible with the Nostr protocol.
4. Convert to NSEC: The private key can then be converted into the NSEC format, which is typically a base64-encoded string.
Way above my pay grade but shall forward onto the person whom asked me the question..🫡
it is definitely doable, a little searching turned up some code that could be used. if there is not already a tool out there, would be a good tool to create. i could probably build a terminal script to do it, just a matter of taking the time
I can barely write my name on a piece of paper never mind code that could be of use 🤣🤣
But I think for ease of access for a normie - having a SF is better than a Nsec
found that this is basically already solved with NIP-6 and nostr-tools has a straightforward implementation. Will see if I can make a UI for it.