Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Structure of CLI #380

Closed
faboweb opened this issue Jan 24, 2018 · 1 comment
Closed

Structure of CLI #380

faboweb opened this issue Jan 24, 2018 · 1 comment

Comments

@faboweb
Copy link
Contributor

faboweb commented Jan 24, 2018

How should the CLI cmd (gaia) be structured?

This probably relates to the decision about multiple binaries in: #379

Quoting @ethanfrey's proposal: (Could you maybe update this to the latest status of the conversation?)

gaia keys ...:
add --password= --type=<ed25519|secp256k1|ledger|...> [--seed='...........']
update --password= --new_password=<new_pass>
delete --password=
list
show

gaia client ...:
init
version
status
serve: start LCD, the local REST server, exposing above endpoints
block [height] [--select=<header|txs|results>]: This will grab the relevant information from the block at the given height (latest if no height provided). This may map to several rpc calls.
validatorset [height]
txs --tag=: search for all tx that match tag
tx : query tx by hash
tx send --name= --password= --to= --amount=<..> ...
tx bond --name= --password= --delegate= --amount=<..> ...
...

@ebuchman
Copy link
Member

Now that #349 is merged let's open more specific issues as needed

ParthDesai pushed a commit to ChorusOne/cosmos-sdk that referenced this issue Apr 19, 2021
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

No branches or pull requests

2 participants