-
Notifications
You must be signed in to change notification settings - Fork 547
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
docs: added a note to distinguish between chain accounts and Ignite accounts #2777
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just need a changelog entry !
or a |
@fadeev I realize that this distinction between For instance, giving the following blogd keys : $ blogd keys list
- name: alice
type: local
address: cosmos1wzuums2e3t3jkz7ym4thjecype5352zds9h96d
pubkey: '{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"AjAuPBMEhuB/BVcJbYvnbsfh3GrQswod3OsiIOWyO/TC"}'
mnemonic: ""
- name: bob
type: local
address: cosmos1l6twp8lkzskpch4wdej5gsee7tuhk9agypjxxa
pubkey: '{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"A/piEG8Yivahuib/AG8XOMUQB4r+YhfbaH8qJk/O9pT8"}'
mnemonic: "" I can query them with
And now I've just reproduced the problem a user has in #2773 !!! If I run It seems like This is related to a migration of the keyring added in v0.46 (cosmos/cosmos-sdk#9695) |
@tbruyelle good to know! 👍 It still might be a good practice to use the chain's binary for key management, but I will expand the description of this command in the following PRs. |
…ccounts (ignite#2777) * docs: added a note to distinguish between chain accounts and Ignite accounts * fix: typo Co-authored-by: Alex Johnson <alex@shmeeload.xyz>
No description provided.