iorveth bf8c282d79 proposals_codex: Remove set_content_working_group_mint_capacity proposal type & related logic před 4 roky
..
src bf8c282d79 proposals_codex: Remove set_content_working_group_mint_capacity proposal type & related logic před 4 roky
CHANGELOG.md 6a508d1d3b runtime changelong update před 4 roky
Cargo.toml 883e559a93 Add content directory dependency před 4 roky
README.md 970187b010 Update runtime/README.md před 4 roky
build.rs 67cd58c4a0 runtime: Restore valid env variable. před 4 roky
runtime-banner.svg 2a532261d6 update README před 5 roky

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 with cargo build --release, 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 Pioneer 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