On macOS:
brew install gmp
brew install openssl
sudo ln -sf /usr/local/opt/openssl@1.1 /usr/local/opt/opensslOn Linux (Ubuntu)
sudo apt install glibc-static gmp-devel gmp-static openssl-libs openssl-static gcc-c++On Linux (Cent OS / Amazon Linux 2)
sudo yum install glibc-static gmp-devel gmp-static openssl-libs openssl-static gcc-c++On macOS:
brew cask install docker
open /Applications/Docker.appOn Linux, reference official documentation here.
For macOS, you can reference this guide. For Linux, you can reference this guide.
Most repos from harmony-one assumes the GOPATH convention. More information here.
Clone and set up all of the repos with the following set of commands:
- Create the appropriate directories:
mkdir -p $(go env GOPATH)/src/github.com/harmony-one
cd $(go env GOPATH)/src/github.com/harmony-oneIf you get 'unknown command' or something along those lines, make sure to install golang first.
- Clone this repo & dependent repos.
git clone https://github.com/harmony-one/mcl.git
git clone https://github.com/harmony-one/bls.git
git clone https://github.com/harmony-one/harmony.git
cd harmony- Build the harmony binary & dependent libs
make
Run
bash scripts/install_build_tools.shto ensure build tools are of correct versions.
Included in this repo is a Dockerfile that has a full harmony development environment and
comes with emacs, vim, ag, tig and other creature comforts. Most importantly, it already has the go environment
with our C/C++ based library dependencies (libbls and mcl) set up correctly for you.
You can build the docker image for yourself with the following commands:
cd $(go env GOPATH)/src/github.com/harmony-one/harmony
make clean
docker build -t harmony .Then you can start your docker container with the following command:
docker rm harmony # Remove old docker container
docker run --name harmony -it -v "$(go env GOPATH)/src/github.com/harmony-one/harmony:/root/go/src/github.com/harmony-one/harmony" harmony /bin/bashNote that the harmony repo will be shared between your docker container and your host machine. However, everything else in the docker container will be ephemeral.
If you need to open another shell, just do:
docker exec -it harmony /bin/bashLearn more about docker here.
The make command should automatically build the Harmony binary & all dependent libs.
However, if you wish to bypass the Makefile, first export the build flags:
export CGO_CFLAGS="-I$GOPATH/src/github.com/harmony-one/bls/include -I$GOPATH/src/github.com/harmony-one/mcl/include -I/usr/local/opt/openssl/include"
export CGO_LDFLAGS="-L$GOPATH/src/github.com/harmony-one/bls/lib -L/usr/local/opt/openssl/lib"
export LD_LIBRARY_PATH=$GOPATH/src/github.com/harmony-one/bls/lib:$GOPATH/src/github.com/harmony-one/mcl/lib:/usr/local/opt/openssl/lib
export LIBRARY_PATH=$LD_LIBRARY_PATH
export DYLD_FALLBACK_LIBRARY_PATH=$LD_LIBRARY_PATH
export GO111MODULE=onThen you can build all executables with the following command:
bash ./scripts/go_executable_build.sh -SReference
bash ./scripts/go_executable_build.sh -hfor more build options
One can start a local network (a.k.a localnet) with your current code using the following command:
make debugThis localnet has 2 shards, with 11 nodes on shard 0 (+1 explorer node) and 10 nodes on shard 0 (+1 explorer node).
The shard 0 endpoint will be on the explorer at
http://localhost:9599. The shard 1 endpoint will be on the explorer athttp://localhost:9598.You can view the localnet configuration at
/test/configs/local-resharding.txt. The fields for the config are (space-delimited & in order)ip,port,mode,bls_pub_key, andshard(optional).
One can force kill the local network with the following command:
make debug-killYou can view all make commands with
make help
To keep things consistent, we have a docker image to run all tests. These are the same tests ran on the pull request checks.
To run this test do:
make test-goThis test runs the go tests along with go lint, go fmt, go imports, go mod, and go generate checks.
To run this test do:
make test-apiThis test starts a localnet (within the Docker container), ensures it reaches consensus, and runs a series of tests to ensure correct Node API behavior. This test also acts as a preliminary integration test (more through tests are done on the testnets).
The tests ran by this command can be found here.
If you wish to debug further with the localnet after the tests are done, open a new shell and run:
make test-api-attachThis will open a shell in the docker container that is running the Node API tests.
Note that the docker container has the Harmony CLI on path, therefore you can use that to debug if needed. For example, one could do
hmy blockchain latest-headersto check the current block height of localnet. Reference the documentation for the CLI here for more details & commands.
Harmony is licensed under the MIT License. See LICENSE file for
the terms and conditions.
Harmony includes third-party open-source code. In general, a source subtree
with a LICENSE or COPYRIGHT file is from a third party, and our
modifications thereto are licensed under the same third-party open source
license.
Also please see our Fiduciary License Agreement if you are contributing to the project. By your submission of your contribution to us, you and we mutually agree to the terms and conditions of the agreement.
See CONTRIBUTING for details.
- Fully sharded network with beacon chain and shard chains
- Sharded P2P network and P2P gossiping
- FBFT (Fast Byzantine Fault Tolerance) Consensus with BLS multi-signature
- Consensus view-change protocol
- Account model and support for Solidity
- Cross-shard transaction
- VRF (Verifiable Random Function) and VDF (Verifiable Delay Function)
- Cross-links
- EPoS staking mechanism
- Kademlia routing
- Resharding
- Integration with WASM
- Fast state synchronization
- Auditable privacy asset using ZK proof