laconicd/README.md
neeraj 0deb273c61
All checks were successful
Protobuf / lint (pull_request) Successful in 25s
Build / build (pull_request) Successful in 2m43s
Lint / Run golangci-lint (pull_request) Successful in 4m11s
E2E Tests / test-e2e (pull_request) Successful in 4m18s
Integration Tests / test-integration (pull_request) Successful in 2m16s
SDK Tests / sdk_tests_nameservice_expiry (pull_request) Successful in 9m44s
SDK Tests / sdk_tests (pull_request) Successful in 10m36s
Unit Tests / test-unit (pull_request) Successful in 2m19s
SDK Tests / sdk_tests_auctions (pull_request) Successful in 13m34s
Update README
2024-04-01 14:58:02 +05:30

48 lines
1019 B
Markdown

<div align="center">
<h1> Laconic Network </h1>
</div>
![banner](docs/laconic.jpeg)
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](https://github.com/cosmos/cosmos-sdk/) which runs on top of [CometBFT](https://github.com/cometbft/cometbft) consensus engine.
## Installation
Install `laconicd`:
```bash
# install the laconicd binary
make install
```
## Usage
Run with a single node fixture:
```bash
# start the chain
./scripts/init.sh
# start the chain with data dir reset
./scripts/init.sh clean
```
## Tests
Run tests:
```bash
# 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:
- [Laconic Twitter](https://twitter.com/laconicnetwork)
- [Website](https://laconic.com)