Laconic state machine
Prathamesh Musale
3c495bbcee
Some checks failed
Build / build (pull_request) Successful in 2m31s
E2E Tests / test-e2e (pull_request) Successful in 3m52s
Integration Tests / test-integration (pull_request) Successful in 1m51s
Lint / Run golangci-lint (pull_request) Successful in 5m4s
SDK Tests / sdk_tests (pull_request) Successful in 8m44s
Unit Tests / test-unit (pull_request) Successful in 1m49s
SDK Tests / sdk_tests_auctions (pull_request) Failing after 12m10s
SDK Tests / sdk_tests_nameservice_expiry (pull_request) Failing after 6m57s
|
||
|---|---|---|
| .gitea/workflows | ||
| api/cerc | ||
| app | ||
| cmd/laconicd | ||
| docs | ||
| gql | ||
| proto | ||
| scripts | ||
| tests | ||
| testutil | ||
| utils | ||
| x | ||
| .dockerignore | ||
| .gitignore | ||
| Dockerfile | ||
| go.mod | ||
| go.sum | ||
| Makefile | ||
| README.md | ||
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: