Skip to content
Joystream Full Node
Branch: master
Clone or download
Latest commit 9ea3cfa Apr 15, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
res athens chainspec Apr 14, 2019
src display correctly encoded ed25519 Authority address Apr 14, 2019
.editorconfig Initial commit Jan 21, 2019
.gitignore
Cargo.lock Cargo.lock Apr 14, 2019
Cargo.toml update latest substrate v1.0 branch Apr 14, 2019
README.md update README Apr 14, 2019
banner.svg update banner.svg Apr 14, 2019
build-clean-start.sh
build-runtime.sh substrate upgrade: refactor to work with latest joystream runtime Apr 3, 2019
build.rs import from new node-template Feb 12, 2019
init-wasm.sh Add init.sh script and improve readme Jan 21, 2019

README.md

 Nodes for Joystream

Joystream Full Node

Joystream node built on top of Substrate.

Follow the instructions below to download the software or build it from source. Further instructions for windows and mac can be found here. Linux should be similar to mac.

Binary releases

Downloads are available in releases.

Building from source

Initial setup

If you want to build from source you will need the Rust toolchain, openssl and llvm/libclang.

git clone https://github.com/Joystream/substrate-node-joystream.git

Initialise the WASM build environment:

cd substrate-node-joystream/
./init-wasm.sh

Building

Clone the joystream runtime into the substrate-node-joystream directory:

git clone https://github.com/Joystream/substrate-runtime-joystream.git

Build the WASM runtime library:

./build-runtime.sh

Build the node (native code):

cargo build --release

Running a public node

Run the node and connect to the public testnet

cargo run --release

Installing a release build

This will install the executable joystream-node to your ~/.cargo/bin folder, which you would normally have in your $PATH environment.

cargo install --path ./

Now you can run

joystream-node

Development

Running a local development node

cargo run --release -- --dev

Cleaning development chain data

When making changes to the runtime library remember to purge the chain after rebuilding the node to test the new runtime.

cargo run --release -- purge-chain --dev
You can’t perform that action at this time.