Mokhtar Naamani 201a5c9998 short election stages for testing runtime, drop alternate runtime spec names 2 éve
..
src 201a5c9998 short election stages for testing runtime, drop alternate runtime spec names 2 éve
CHANGELOG.md f0bc38390c giza: update readme, changelog some setup instructions and small fix to yarn.lock 2 éve
Cargo.toml 131a7fa022 bump runtime 2 éve
README.md 23a386b098 Remove Pioneer 2 éve
build.rs e6fa74ba0a Merge pull request #2514 from shamil-gadelshin/storage_node_v2 3 éve
runtime-banner.svg 2a532261d6 update README 4 éve

README.md

Joystream Runtime

Joystream Runtime

The runtime is the code that defines the consensus rules of the Joystream protocol. It is compiled to WASM and lives on chain. Joystream node execute the code's logic to validate transactions and blocks on the blockchain.

When building joystream-node as described in ../node/README.md, in addition to the joystream-node binary being built the WASM blob artifact is produced in:

./target/release/wbuild/joystream-node-runtime/joystream_node_runtime.compact.wasm

Deployment

Deploying the compiled runtime on a live system can be done in one of two ways:

  1. By creating a proposal for upgrading the Joystream runtime, which will then be voted on by the council. If the proposal is approved, the upgrade will go through after a grace period. When the Joystream platform is live, this will be the only way to upgrade the chain's runtime code.

  2. By creating an extrinsic (transaction) signed with the sudo key invoking system::setCode(). This can be done either from the polkadot-js/apps extrinsics tab, or directly with an admin script. This way of upgrading the runtime code is intended for development and testnet phases only.

Versioning the runtime

Versioning of the runtime is set in runtime/src/lib.rs For detailed information about how to set correct version numbers when developing a new runtime, see this