Build your runtime deterministically
The following guide shows how to build deterministic runtimes.
Last updated
Was this helpful?
Appchains on Polkadot
The following guide shows how to build deterministic runtimes.
Last updated
Was this helpful?
By default, the Rust compiler generates optimized Wasm binaries, but they aren't always deterministically reproducible. If the Wasm runtime isn't deterministic, each build might produce slightly different bytecode, This can be a problem for blockchain networks where every node must run the exact same runtime.
To ensure deterministic Substrate runtime builds, Pop CLI integrates . SRTool guarantees that every runtime build produces identical Wasm bytecode, making it reliable for production use.
This build requires or to be installed and running. Pop CLI automatically invokes the SRTool image to generate a reproducible and verifiable runtime.
This guide provides a quick overview of the importance of deterministic builds and how to achieve them using Pop CLI:
While generating your chain spec with pop build spec, Pop CLI also gives you the option to build your runtime deterministically and inject it automatically.
Once you select the option to build deterministically, Pop CLI will prompt you to provide the runtime path (by default it's typically located in the runtime/ folder). After confirming, the deterministic build process will begin.
⏳ The build may take 10–15 minutes or more, depending on your setup, so be patient!
Once the build is complete, Pop CLI will automatically inject the resulting runtime code into your generated chain spec.
If you'd prefer not to be prompted interactively, you can specify everything up front via command line:
Technical Support
🧑🏫 in the Polkadot docs is a good starting point.
🧑🔧 For technical introduction, .
Create a question and tag it with ""
Share the StackExchange question in our