Add age-keygen-det to Tools#47
Open
dmonakhov wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tool which encode raw hex32 entropy as age private key.
People who already secure a BIP-39 mnemonic have, over the years, built up a lot of practice around it: paper backups, metal plates, geographic redundancy, seed-sharding schemes (SeedXOR, etc.), and air-gapped hardware-wallet workflows. BIP-85 layers application-specific entropy derivation on top of that same root, and any 32-byte output of BIP-85's HEX application is a valid input for age-keygen-det. So the "where do I back up my age key" problem reduces to the already-solved "where do I back up my BIP-39 seed" problem - no new physical procedure, no new envelope, no parallel sharding plan.