gaiad UX issues

[ebuchman]

This is a collection of issues I've been accumulating using the CLI. Apologies if there are some duplicates here or there's not that much detail, just wanted to publish this somewhere since I've mentioned it a few times. I believe these all exist in v4.2.1 but the list got started a few months ago so some things might be stale

More generally, I think the whole key system should conceivably be broken out of the SDK or be on an independent release cycle and product strategy. We probably need a key management solution that is generic across chains/binaries as well, so you can use one tool to manage all your keys across all the chains, and even sign txs and stuff (of course you need specific binaries to generate specific kinds of txs).

I built the multisig tool to start to address this multi-chain need, but its very rough and just shells out to underlying binaries.

• --multisig should accept a name, not just an address (@likhita-809 )feat: multisig should accept name, not just address #9553
• When using --offline and --generate-only the key names are no longer recognized, have to use an address (tracking separately in When using --offline and --generate-only the key names are no longer recognized, have to use an address #9837 ) (@atheeshp )
• the default tx broadcast mode claims to be sync but it's actually commit and it often times out. (fix: update simapp to use correct default broadcast mode #9408)
• when tx broadcast times out it doesnt give you the tx id (@alexanderbez)
• can't easily edit key names (@technicallyty) feat!: key rename cli command #9601
• ledger does Account confirm twice on send
• ledger shows uatoms :(
• shouldn't have to use uatoms at all, should add support for writing amounts in atoms
• how to get individual pubkeys from a multisig?
• when creating a new chain cant specify the staking token, need to edit the genesis file (@likhita-809) feat: specify staking bond_denom when creating a new chain #9776
• when creating a new chain, maybe a command to edit arbitrary fields in the json would be nice (tho I guess this is just about some jq fu, maybe that could at least be document to guide users) (tracking separately in Add jq command to help users in editing json #9908 ) (@atheeshp )
• --sequence doesnt work on its own, requires offline and account-number (often need to overwrite the sequence to sign a bunch of sequential multisig txs before they all broadcast) (@likhita-809 ) (tracking seperately in feat: make sequence flag work on its own #9784)
• setting --max-msgs along with --generate-only gives a weird error: Error: cannot use broadcast mode sync with max-msgs != 0. Why would setting the max message have any impact on which broadcast mode you can use?! (tracking separately in setting --max-msgs along with --generate-only gives error #10841 )
• there should be some simple workflow for making a multi msg tx - eg. for building a tx that does reward withdrawal and redelegation in one tx
• chain-id shouldn't be required for creating a tx with --generate-only and --offline (@likhita-809) (tracking separately in feat: tx with generate-only and offline shouldn't use chain id #10710)
• separate general tx flags (eg. sequence, account, chain-id, etc.) from specific tx flags (eg. --msg-type for authz, etc.) so its easier to see.

I'll keep adding to this list as I come across things

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[alexanderbez]

Thanks for this @ebuchman. I'm gonna take a stab at a few 👍

[ebuchman]

Awesome thanks @alexanderbez !!

[clevinson]

@alexanderbez Can you make a note if there are any other of these items that you plan on working on by putting your name next to the checkbox or something?

We're happy to take some of these on our team's side as well, but want to make sure we don't duplicate work.

[alexanderbez]

I haven't had time to tackle anymore since. I'll attach my name to a few that I intend to do shortly.

[blushi]

Regarding "can't easily edit key names" item, is it ok if we add a subcommand like ./simd keys rename? @ebuchman

[technicallyty]

Should we just add a test for an example of: how to get individual pubkeys from a multisig? I divvied up a quick one in this branch. Can make a PR if it seems valuable.

[likhita-809]

--sequence doesnt work on its own, requires offline and account-number (often need to overwrite the sequence to sign a bunch of sequential multisig txs before they all broadcast) (@likhita-809 )

@ebuchman #9784 (comment) can you answer this ?

[atheeshp]

how to get individual pubkeys from a multisig?

@AmauryM may I work on this? or can be ignored?

[ebuchman]

Thanks for all the work on these, really appreciate the improvements! A few others i've opened recently:

• check key is part of multisig when signing - Prevent signing from wrong key in multisig #12328
• can't find keys with os backend after upgrade to v0.44 - Can't find keys with os backend after upgrade to gaia v6 #10877
• keys list with os backend requires entering your password for each key - keys list with keyring-backend=os requires you to enter your password once per key :o  #10875

[tac0turtle]

• lots of the cli items have been pushed into autocli.
• ledger got an update with sign mode textual.
• multisigs are tracked in another issue