prathamesh
576569fe66
Integration Tests / test-integration (push) Successful in 2m33s
E2E Tests / test-e2e (push) Successful in 3m48s
Lint / Run golangci-lint (push) Successful in 5m41s
Unit Tests / test-unit (push) Successful in 1m51s
SDK Tests / sdk_tests_nameservice_expiry (push) Successful in 7m31s
SDK Tests / sdk_tests (push) Successful in 7m53s
SDK Tests / sdk_tests_auctions (push) Successful in 13m48s
Part of cerc-io/laconic2d#32 and cerc-io/laconic2d#33 - Update context used in root command with Viper so that it recognizes the client config from home directory passed in CLI flags - Avoid providing default home dir to depinject so that the home directory passed in CLI flags is used in txs - Known issue: The client config from non-default home directory still doesn't seem to be getting used for some commands; in such cases, user has to pass the required flags explicitly Reviewed-on: cerc-io/laconic2d#34 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: