Laconic state machine
Roy Crihfield
92e3a4d8f4
update protobuf usage note: 2025/01/15 13:16:22 Message cerc.registry.v1.Record contains the reserved field name cerc.registry.v1.Record.type which conflicts with protoreflect.Message interface implementation. This field will be suffixed with an underscore '_'. If you can change the message field name, please do so. In a future iteration of pulsar we may make a breaking change to this practice in order to be compliant with field naming of the original golang protobuf implementation. |
||
|---|---|---|
| .gitea/workflows | ||
| api/cerc | ||
| app | ||
| cmd/laconicd | ||
| docs | ||
| gql | ||
| nitro | ||
| proto | ||
| scripts | ||
| tests | ||
| utils | ||
| x | ||
| .dockerignore | ||
| .gitignore | ||
| .golangci.yml | ||
| 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: