Laconic state machine
Go to file
Prathamesh Musale 4c0cb6c2c4
All checks were successful
Integration Tests / test-integration (push) Successful in 2m37s
E2E Tests / test-e2e (push) Successful in 4m4s
Lint / Run golangci-lint (push) Successful in 5m24s
Unit Tests / test-unit (push) Successful in 1m55s
SDK Tests / sdk_tests_nameservice_expiry (push) Successful in 7m34s
SDK Tests / sdk_tests (push) Successful in 8m13s
SDK Tests / sdk_tests_auctions (push) Successful in 13m23s
Publish on release / Run docker build and publish (release) Successful in 2m27s
Unset home and keyring dir from depinject client config (#35)
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>
2024-07-16 03:50:08 +00:00
.gitea/workflows Rename laconic2d to laconicd (#26) 2024-04-01 09:57:26 +00:00
api/cerc Rename laconic2d to laconicd (#26) 2024-04-01 09:57:26 +00:00
app Rename laconic2d to laconicd (#26) 2024-04-01 09:57:26 +00:00
cmd/laconicd Unset home and keyring dir from depinject client config (#35) 2024-07-16 03:50:08 +00:00
docs Additional CI workflows (#16) 2024-03-07 09:11:53 +00:00
gql Rename laconic2d to laconicd (#26) 2024-04-01 09:57:26 +00:00
proto Rename laconic2d to laconicd (#26) 2024-04-01 09:57:26 +00:00
scripts Replace alpine with ubuntu as base image in the Dockerfile (#31) 2024-07-10 14:36:09 +00:00
tests Replace alpine with ubuntu as base image in the Dockerfile (#31) 2024-07-10 14:36:09 +00:00
testutil Rename laconic2d to laconicd (#26) 2024-04-01 09:57:26 +00:00
utils Use custom KV store config to handle progressively increasing gas usage (#30) 2024-06-25 06:33:41 +00:00
x Use custom KV store config to handle progressively increasing gas usage (#30) 2024-06-25 06:33:41 +00:00
.dockerignore Additional CI workflows (#16) 2024-03-07 09:11:53 +00:00
.gitignore Add initialization script and a Dockerfile (#15) 2024-03-07 05:10:41 +00:00
Dockerfile Replace alpine with ubuntu as base image in the Dockerfile (#31) 2024-07-10 14:36:09 +00:00
go.mod Rename laconic2d to laconicd (#26) 2024-04-01 09:57:26 +00:00
go.sum Setup and integrate GQL server (#12) 2024-02-29 12:45:38 +00:00
Makefile Rename laconic2d to laconicd (#26) 2024-04-01 09:57:26 +00:00
README.md Rename laconic2d to laconicd (#26) 2024-04-01 09:57:26 +00:00

Laconic Network

banner

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: