Skip to content

fix: make keys command more intuitive#6

Merged
AaronCQL merged 2 commits intomainfrom
aaron/fix-keys-cmd
Mar 16, 2026
Merged

fix: make keys command more intuitive#6
AaronCQL merged 2 commits intomainfrom
aaron/fix-keys-cmd

Conversation

@AaronCQL
Copy link
Contributor

Changes

Generate a new key:

jup keys add <name>

Import from a JSON file generated via solana-keygen:

jup keys add <name> --file /path/to/solana-keygen.json

Import from private key or seed phrase:

jup keys add <name> --seed-phrase "word1 word2 ..."
jup keys add <name> --seed-phrase "word1 word2 ..." --derivation-path "m/44'/501'/0'/0'" # optional, defaults to "m/44'/501'/0'/0'"
jup keys add <name> --private-key <key> # accepts hex, base58, base64, or a JSON byte array

Closes #4

@cavemanloverboy
Copy link

fan of this

@AaronCQL AaronCQL merged commit b8cd247 into main Mar 16, 2026
4 checks passed
@AaronCQL AaronCQL deleted the aaron/fix-keys-cmd branch March 16, 2026 16:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

adding keys is not intuitive

2 participants