./simd keys list shows no keys after successful add

[eswenson1]

I’m a complete noob here. I installed the cosmos sdk and then tried to follow the tutorial using the .simapp sample app. I got to the point in the tutorial where I started up the single-node blockchain. That seemed to work fine. I created another console window and attempted the next step in the tutorial which is to query the bank balance for the b9lab account. When I did, I got the error message that b9lab is not a valid name or address: decoding bech32 failed: invalid bech32 string length 5. I did a ./simd key list and see that there are no keys. I then went back to the window where the single node blockchain was running and aborted (^C) and tried the same command there, and I got the same error.

So what gives? Everything was going perfectly well until I created a new console window. Now, nothing seems to work any more. I see that the genesis.json does show all the state that it should – I simply don’t have any keys accessible now.

[julienrbrt]

Which keyring backend have you used?

[eswenson1]

I believe the backend is os. I didn't change anything in the cosmos-sdk -- just pulled the source and built the sample application simd and ran it as per the tutorial. I'm running under macOS Ventura.

I found the os value for keyring-backend in the ~/.simapp/config/client.toml file.

[atheeshp]

Hey @eswenson1, it would be helpful to look-in if you can give the list of commands that you ran from the beginning and also the complete error log.

[eswenson1]

I followed (exactly) the metrications here: https://tutorials.cosmos.network/tutorials/3-run-node/

All the steps in the first console window, up until and including when I started the single-node server worked just fine. And this meant that the key ring was fine and contained the two keys associated with the transfer of stake. Once I started the server, the steps in this tutorial required a new console window. In it, I was unable to execute (successfully) the first command:

$ ./simd query bank balances $(./simd keys show b9lab -a)

The command was unable to find the b9lab key that had successfully been added before starting simd.

As for full logs, where would I find them?

(All of this was done on macOS).

[julienrbrt]

could you tell us which simd version you are using? (simd version --long)
This tutorial seems to use an deprecated version of the SDK.

[eswenson1]

Here is the output of the version command:

➜  build git:(a7e19ad45) ./simd version --long
name: sim
server_name: simd
version: 0.42.6
commit: a7e19ad4588bcceeeeab522f5807b9ff22e91a8c
build_tags: netgo,ledger
go: go version go1.20.4 darwin/amd64
build_deps:
- github.com/99designs/keyring@v1.1.6
- github.com/ChainSafe/go-schnorrkel@v0.0.0-20200405005733-88cbf1b4c40d
- github.com/Workiva/go-datastructures@v1.0.52
- github.com/armon/go-metrics@v0.3.8
- github.com/beorn7/perks@v1.0.1
- github.com/bgentry/speakeasy@v0.1.0
- github.com/btcsuite/btcd@v0.21.0-beta
- github.com/cespare/xxhash/v2@v2.1.1
- github.com/confio/ics23/go@v0.6.6
- github.com/cosmos/go-bip39@v1.0.0
- github.com/cosmos/iavl@v0.16.0
- github.com/cosmos/ledger-cosmos-go@v0.11.1
- github.com/cosmos/ledger-go@v0.9.2
- github.com/davecgh/go-spew@v1.1.1
- github.com/dvsekhvalnov/jose2go@v0.0.0-20200901110807-248326c1351b
- github.com/enigmampc/btcutil@v1.0.3-0.20200723161021-e2fb6adb2a25
- github.com/felixge/httpsnoop@v1.0.1
- github.com/fsnotify/fsnotify@v1.4.9
- github.com/go-kit/kit@v0.10.0
- github.com/go-logfmt/logfmt@v0.5.0
- github.com/gogo/gateway@v1.1.0
- github.com/gogo/protobuf@v1.3.3 => github.com/regen-network/protobuf@v1.3.3-alpha.regen.1
- github.com/golang/protobuf@v1.5.2
- github.com/golang/snappy@v0.0.3-0.20201103224600-674baa8c7fc3
- github.com/google/btree@v1.0.0
- github.com/google/orderedcode@v0.0.1
- github.com/gorilla/handlers@v1.5.1
- github.com/gorilla/mux@v1.8.0
- github.com/gorilla/websocket@v1.4.2
- github.com/grpc-ecosystem/go-grpc-middleware@v1.3.0
- github.com/grpc-ecosystem/grpc-gateway@v1.16.0
- github.com/gtank/merlin@v0.1.1
- github.com/gtank/ristretto255@v0.1.2
- github.com/hashicorp/go-immutable-radix@v1.0.0
- github.com/hashicorp/golang-lru@v0.5.4
- github.com/hashicorp/hcl@v1.0.0
- github.com/keybase/go-keychain@v0.0.0-20190712205309-48d3d31d256d
- github.com/libp2p/go-buffer-pool@v0.0.2
- github.com/magiconair/properties@v1.8.5
- github.com/mattn/go-isatty@v0.0.12
- github.com/matttproud/golang_protobuf_extensions@v1.0.1
- github.com/mimoo/StrobeGo@v0.0.0-20181016162300-f8f6d4d2b643
- github.com/minio/highwayhash@v1.0.1
- github.com/mitchellh/go-homedir@v1.1.0
- github.com/mitchellh/mapstructure@v1.3.3
- github.com/mtibben/percent@v0.2.1
- github.com/pelletier/go-toml@v1.8.1
- github.com/pkg/errors@v0.9.1
- github.com/pmezard/go-difflib@v1.0.0
- github.com/prometheus/client_golang@v1.10.0
- github.com/prometheus/client_model@v0.2.0
- github.com/prometheus/common@v0.23.0
- github.com/prometheus/procfs@v0.6.0
- github.com/rakyll/statik@v0.1.7
- github.com/rcrowley/go-metrics@v0.0.0-20200313005456-10cdbea86bc0
- github.com/regen-network/cosmos-proto@v0.3.1
- github.com/rs/cors@v1.7.0
- github.com/rs/zerolog@v1.21.0
- github.com/spf13/afero@v1.3.4
- github.com/spf13/cast@v1.3.1
- github.com/spf13/cobra@v1.1.3
- github.com/spf13/jwalterweatherman@v1.1.0
- github.com/spf13/pflag@v1.0.5
- github.com/spf13/viper@v1.7.1
- github.com/stretchr/testify@v1.7.0
- github.com/subosito/gotenv@v1.2.0
- github.com/syndtr/goleveldb@v1.0.1-0.20200815110645-5c35d600f0ca
- github.com/tendermint/btcd@v0.1.1
- github.com/tendermint/crypto@v0.0.0-20191022145703-50d29ede1e15
- github.com/tendermint/go-amino@v0.16.0
- github.com/tendermint/tendermint@v0.34.11
- github.com/tendermint/tm-db@v0.6.4
- github.com/zondax/hid@v0.9.0
- golang.org/x/crypto@v0.0.0-20201221181555-eec23a3978ad
- golang.org/x/net@v0.0.0-20201021035429-f5854403a974
- golang.org/x/sys@v0.0.0-20210510120138-977fb7262007
- golang.org/x/term@v0.0.0-20201117132131-f5c789dd3221
- golang.org/x/text@v0.3.3
- google.golang.org/genproto@v0.0.0-20210114201628-6edceaf6022f
- google.golang.org/grpc@v1.37.0 => google.golang.org/grpc@v1.33.2
- google.golang.org/protobuf@v1.26.0
- gopkg.in/ini.v1@v1.61.0
- gopkg.in/yaml.v2@v2.4.0
- gopkg.in/yaml.v3@v3.0.0-20200313102051-9f266ea9e77c
cosmos_sdk_version: ""

➜  build git:(a7e19ad45)

I'm wondering if this isn't some issue with the OS keyring (macOS). If you haven't seen this problem on Linux, it might be a Mac keyring issue.

[eswenson1]

This is very interesting. It "started working" -- but let me explain what I did.

First of all, I let my machine sit for a few days without touching simapp. Before I stopped playing with simapp last week, I aborted the running simd server, since it was just spewing out log messages over and over (this might be another issue). This morning, after I saw your request for version info, I did the following:

I restarted the simd server in the original console window. I got a macOS prompt to allow the app to access the keyring (keychain access must have timed out). I provided my macOS password and selected "Always Allow". The server started up and macOS asked me if I wanted to allow inbound connections to the server -- I said yes. Then I went to the "other" console window, where the tutorial had had me issue the ./simd query bank balances $(./simd keys show b9lab -a) command. I simply executed ./simd keys show b9lab -a and this time it worked. I was able to query the balance for b9lab, create the "student" key, and transfer 10stake from the b9lab to the student account. This all worked perfectly.

Why it didn't work last week is a mystery to me -- since I didn't "do" anything differently this time other than to allow time to pass and to restart the simd server.

[julienrbrt]

Great that you have found the issue!
I would, however, greatly encourage you to use v0.46.x given that all previous versions have been deprecated.

[eswenson1]

Will do. Thanks. You might get the site updated to reflect that version as the one to use for the simapp tutorial too.