Skip to content

Runtime upgrades ​

All runtime changes since genesis relaunch (2026-08-31) go through set_code on the same genesis hash 0xe973931eb0041952249c6a5f6d66537ced5acfe7e1334c44b531ddbbffeae7aa. That is the same chain with a new runtime, not a relaunch.

Example: spec 251 landed in block 822,147 (extrinsic submitted in 822,142), hash 0x82027ae9…d05cc1. transaction_version stayed 12. The chain kept producing during the upgrade (822,142 → 822,147 before the script signed off).

Live specVersion is read from RPC (255 on 2026-11-20). It will keep moving. Governance has shipped upgrades without sudo (226–227).

What set_code does not do ​

RPC lives in the node binary. emp_* SS58 handling is a binary bug on the validators. Shipping 251 and 255 did not fix it. See RPC surface.

A new runtime does not upgrade empoorio-node on disk. Operators must deploy the binary separately when node-side RPC or networking changes.

Clients ​

specVersion in the implicit payload must match. A bump of spec alone does not invalidate signatures. A bump of transactionVersion does — rebuild the envelope and the signed-extension list from metadata.

CheckPqcPolicy extra bytes have been stable since spec 223 (transaction_version 7). Later spec bumps did not change those two bytes.

Holes and migrations ​

Retired pallet indices stay holes. MultiBlockMigrations (146) is the multi-block migrator. Do not insert a pallet in the middle of construct_runtime!.

How to verify after an upgrade ​

bash
curl -s https://rpc2.testnet.empooriochain.com \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"state_getRuntimeVersion","params":[]}'

Then chain_getBlockHash(0) still equals genesis. If genesis moved, you are on a different chain.

English technical docs. Marketing lives at empooriochain.com.