gdnathan / edgeware-node

Issue #4 : Bounty: Metadata needs to be updated to v14

edgeware-node

Edgeware is a proof-of-stake smart contract blockchain with a community-managed treasury, decentralized proposal system, and network of DAOs.

A getting started guide can be found at our Github Wiki, including guides for running a node, validating, and setting up basic monitoring tools to keep your node online.

For more details about the project, visit the Edgeware website, or check out the blog or Twitter. Finally, for discussion and governance, campaigns and proposals can be found on Commonwealth.

Quickstart

If your device is clean (such as a fresh cloud VM) you can use this script for an automated setup: ./setup.sh

Install system dependencies:

• Linux: sudo apt install cmake pkg-config libssl-dev git clang libclang-dev
• Mac: brew install cmake pkg-config openssl git llvm

Install Edgeware dependencies:

curl https://sh.rustup.rs -sSf | sh
rustup update stable
rustup update nightly
rustup target add wasm32-unknown-unknown --toolchain nightly

Build Edgeware:

cargo build --release

Build for Edgeware's Beresheet testnet, which uses a different runtime version and EVM chain ID:

cargo build --release --features beresheet-runtime

Build a WASM runtime to be deployed on-chain using srtool:

cargo install --git https://github.com/chevdor/srtool-cli
srtool build --package edgeware-runtime --runtime-dir node/runtime . --app --json

Build a WASM runtime for Beresheet:

srtool build --package edgeware-runtime --runtime-dir node/runtime . --app --json --build-opts="--features=beresheet-runtime"

Ensure you have a fresh start if updating from another version:

./scripts/purge-chain.sh <NETWORK_NAME_ID>

To start up the Edgeware node and connect to the Mainnet, run:

./target/release/edgeware --chain=edgeware --name <INSERT_NAME> --wasm-execution Compiled

To start up the Edgeware node and connect to the Beresheet testnet, run:

./target/release/edgeware --chain=beresheet --name <INSERT_NAME>

Docker

Compile in Docker

To run a local build using docker, run:

docker build -f docker/Dockerfile .

Images that have failed to build typically are hard to remove. The best way to reclaim the wasted space is to uninstall Docker and then reinstall.

If the above image failed to compile edgeware-cli, then it's because your machine doesnt have enough memory; or your docker doesn't have enough memory available. Try and increase Docker's available memory by a few notches, by going to Docker Desktop settings.

Pull image and run (no compile)

If you want to use our previously-built image depthhoar/edgeware-node:v3.3.3, you can use docker-compose:

cd docker; docker-compose up

You will have exposed ports 9933, 9944 and 30333.

Then run:

docker run --rm -it depthhoar/edgeware-node:v3.3.3 edgeware --chain=edgeware --name <INSERT NAME> --wasm-execution Compiled

Benchmarking

To build in benchmarking mode:

cargo build --features runtime-benchmarks --release

To run benchmarks and output new weight files while still in the node/cli folder (replace signaling with voting to benchmark voting instead):

../../target/release/edgeware benchmark --pallet signaling --extrinsic "*" --steps 50 --repeat 20 --output ../runtime/src/weights/

If the amount of time it takes to run the benchmark is too long, consider reducing the steps and repeat parameters.