substrate-package | Known working releases of the Substrate Node Template | Blockchain library

You need to be a contributor of substrate-developer-hub/substrate-package in order to be able to push back to that repository.

If you need to make modifications, you should:

• fork that repository
• add the fork as a submodule
• make changes in it, add, commit and push: the push will work, since it is your own repository.
• make a PR (Pull Request) to the original forked repository if you want your changes integrated back.

Let's try to address a few of the different topics you asked:

what is the difference behind build.sh and cargo build

The Substrate runtime is compiled to both a Native binary and a Wasm blob. In Substrate v1.0, these compilation steps are separate. build.sh compiles your runtime to Wasm, while cargo build compiles your entire node (like the CLI, database, etc..) including a native version of your runtime.

It seems that without purge-chain both the substrate_node_template_runtime_wasm.compact.wasm and ./target/release/node-name are not updated.

It is important to understand the specifics happening in the background here. When you run a node, a database is stored locally which has your chain state. So if you start a node with ./target/release/node-name --dev for 50 blocks, stop the node, and then start it again, it will continue right where you left off (at block 51).

Remember that as part of your node's genesis configuration, the Runtime Wasm is stored on chain, and used to determine which version of the runtime you should run (native vs Wasm).

If you recompile your Wasm and your Native binary, and run it without doing anything else, you will see no differences. Even though your node binary is totally new and updated, it is using the same database with the old chain state. This means that in your database, you also have the old Wasm, and when the node does it's check for which version to use, it will fallback to use the Wasm from your database!

If you want your node to pull the latest changes you made, you can do one of two things:

1. Trigger an on-chain upgrade of your Wasm runtime. This will make your database have the latest runtime code, and thus your node would use the latest changes.

2. Purge your chain to restart your genesis. This will delete any old state of your Substrate blockchain, and ultimately populate the chain state with the latest Wasm runtime, which should agree with your node.

My suggestion of: