forked from cerc-io/laconicd
prathamesh
4c0cb6c2c4
Part of #33 Follows PR #34 - With earlier workaround in root cmd (not passing `DefaultNodeHome` to depinject), it created a `config/client.toml` wherever the laconicd CLI was being run - Unset `clientCtx.HomeDir` and `clientCtx.KeyringDir` while providing client context to depinject instead to prevent this and still handle the `--home` flag precedence issue - When using default home directory, all commands still work as `DefaultNodeHome` is passed to the [command executor](https://git.vdb.to/cerc-io/laconic2d/src/branch/main/cmd/laconicd/main.go#L18) Reviewed-on: cerc-io/laconic2d#35 Co-authored-by: Prathamesh Musale <prathamesh.musale0@gmail.com> Co-committed-by: Prathamesh Musale <prathamesh.musale0@gmail.com>
Laconic Network
The Source of Proof. Laconic is a next generation data availability & verifiability layer with cryptographic proofs, powering internet-scale Web3 applications, built on Proof-of-Stake with fast-finality using the Cosmos SDK which runs on top of CometBFT consensus engine.
Installation
Install laconicd:
# install the laconicd binary
make install
Usage
Run with a single node fixture:
# start the chain
./scripts/init.sh
# start the chain with data dir reset
./scripts/init.sh clean
Tests
Run tests:
# integration tests
make test-integration
# e2e tests
make test-e2e
Community
The following chat channels and forums are a great spot to ask questions about Laconic: