Skip to content
This repository has been archived by the owner on Jan 22, 2025. It is now read-only.

Add solana-keygen #593

Closed
garious opened this issue Jul 12, 2018 · 0 comments
Closed

Add solana-keygen #593

garious opened this issue Jul 12, 2018 · 0 comments
Assignees
Milestone

Comments

@garious
Copy link
Contributor

garious commented Jul 12, 2018

The problem:

solana-mint > id.json
solana-wallet airdrop --tokens=123 --mint=id.json
solana-fullnode-config > validator.json     <---- doh! not the keypair from id.json

Related mess: We're using solana-mint as identity files because it happens to generate new keypairs. Then in solana-wallet, we call the parameter --mint because it's in the Mint JSON format and otherwise has no relationship to the Mint's file format.

There should be no solana-mint and instead just a solana-keygen. To get a token count to solana-genesis, we'd pass that in as a CLI option instead of through mint.json.

By default, solana-keygen should create ~/.config/solana/id.json and include a CLI option to change that path. The format of the file could either be Vec[u8] or a base58-encoded string.

Likewise, by default, solana-wallet and solana-fullnode should look for id.json in the home directories. solana-genesis, on the other hand, should point to a different location explicitly for the Mint's identity file.

Here's what the new workflow would look like:

solana-keygen
solana-wallet airdrop --tokens=123
solana-fullnode-config > validator.json     <---- w00t! the keypair from ~/.config/solana/id.json

And for genesis:

solana-keygen -o - | solana-genesis -o genesis.log
@garious garious added this to the v0.7.0 milestone Jul 12, 2018
garious added a commit to garious/solana that referenced this issue Jul 12, 2018
garious added a commit that referenced this issue Jul 13, 2018
vkomenda pushed a commit to vkomenda/solana that referenced this issue Aug 29, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants