the chain-id needs to be set before anything else (#25)
All checks were successful
E2E Tests / test-e2e (push) Successful in 4m27s
Lint / Run golangci-lint (push) Successful in 5m6s
Integration Tests / test-integration (push) Successful in 2m25s
SDK Tests / sdk_tests_nameservice_expiry (push) Successful in 8m12s
SDK Tests / sdk_tests_auctions (push) Successful in 13m56s
Unit Tests / test-unit (push) Successful in 2m26s
SDK Tests / sdk_tests (push) Successful in 9m6s

otherwise this error presents itself silently:

```
updated config is invalid: client config invalid: chain-id is empty
```

Co-authored-by: zramsay <zach@bluecollarcoding.ca>
Reviewed-on: cerc-io/laconic2d#25
Co-authored-by: zramsay <zramsay@noreply.git.vdb.to>
Co-committed-by: zramsay <zramsay@noreply.git.vdb.to>
This commit is contained in:
zramsay 2024-04-01 12:19:54 +00:00 committed by nabarun
parent 213c390c37
commit 6bc3d2fcde

View File

@ -21,8 +21,8 @@ if [ "$1" == "clean" ] || [ ! -d "$HOME/.laconicd/data/blockstore.db" ]; then
make install
fi
laconicd config set client keyring-backend $KEYRING
laconicd config set client chain-id $CHAINID
laconicd config set client keyring-backend $KEYRING
# if $KEY exists it should be deleted
laconicd keys add $KEY --keyring-backend $KEYRING