forked from cerc-io/laconicd-deprecated
Michael
facd64a14b
* first pass use tests/sdk-tests/run-tests.sh in github action * - -> _ * diagnostic env step * diagnostic env step * diagnostic env step does not support cwd * checkout not preserved between actions * ./ missing * start built containers * missing unmarshalling of content bytes before encoding and generation of CID * unchecked error complaint from linter * golang linting is really picky * utils/json test for comparing known, but deprecated method to new implementation * try curl (retval 0) instead of wget (retval 8) for 404 that is returned * missing curl for health check * use feature branch for laconic-sdk... UNDO THIS LATER * checkout is done from inside of container, rather than copied in from filesystem. checking out dev branch for now * docker network inspect for diagnostic * docker network inspect for diagnostic missing arg * listen on 0.0.0.0 specfically * trying localhost * try host mode network * host mode breaks name resolution of containers * manual service check in laconicd container for diagnostic * revert ListenAndServe * sleep and docker logs... appears endpoint is not coming up maybe? * disable fail_ci on codecov error... it is unstable * turn codecov back to fail on error true to avoid invisible failure. * Cleanup for whitespace and require.NoError in test * new json util test, turning off codecov fails CI, and gitignore for test artifacts
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 Tendermint Core consensus engine.
Note: Requires Go 1.19+
Installation
make install
Usage
To quickly get started with a single node fixture, run:
./init.sh
Community
The following chat channels and forums are a great spot to ask questions about Ethermint:
Contributing
Looking for a good place to start contributing? Check out some good first issues.
For additional instructions, standards and style guides, please refer to the Contributing document.