Khala Network Runtime 1130

The runtime 1130 contains the following major updates:

1. Enable the Gemini Update (tokenomic update and bug fixes)

Upgrade instructions

This upgrade is mainly an on-chain runtime upgrade. A new client is released and recommended to upgrade, but not required. Existing downstream consumers (including pherry and PRB), and all the clients relying on the recent version of polkadot.js can automatically handle the upgrade. It's suggested to keep monitoring the nodes to make sure they will operate normally.

However if you are one of the following roles, you should follow the instructions:

For transaction signers: If you sign transactions with any 3rd party Substrate client which cannot deal with the runtime upgrade (i.e. subxt, GSRPC), you will need to restart or reload the client after the runtime upgrade applies. Otherwise you may get invalid signatures. Polkadot.js based clients should be able to automatically pick up the new metadata.

For index services: Please carefully examine the indexer after the runtime upgrade to make sure it operates properly.

Khala Network Runtime 1120

The runtime 1120 contains the following major updates:

1. Fix XCM origin issue (#75)
2. Enable kUSD (#74)

Upgrade instructions

This upgrade is mainly an on-chain runtime upgrade. A new client is released and recommended to upgrade, but not required. Existing downstream consumers (including pherry and PRB), and all the clients relying on the recent version of polkadot.js can automatically handle the upgrade. It's suggested to keep monitoring the nodes to make sure they will operate normally.

However if you are one of the following roles, you should follow the instructions:

For transaction signers: If you sign transactions with any 3rd party Substrate client which cannot deal with the runtime upgrade (i.e. subxt, GSRPC), you will need to restart or reload the client after the runtime upgrade applies. Otherwise you may get invalid signatures. Polkadot.js based clients should be able to automatically pick up the new metadata.

For index services: Please carefully examine the indexer after the runtime upgrade to make sure it operates properly.

Khala Network Runtime 1110

The runtime 1110 contains the following major updates:

1. Add SubBridge pallets (xtransfer) to enable XCM token transfer and XCM-ChainBridge relay
2. Enable crosschain assets registration
3. Update the upstream to polkadot-v0.9.16

Upgrade instructions

This upgrade is mainly an on-chain runtime upgrade. A new client is released and recommended to upgrade, but not required. Existing downstream consumers (including pherry and PRB), and all the clients relying on the recent version of polkadot.js can automatically handle the upgrade. It's suggested to keep monitoring the nodes to make sure they will operate normally.

However if you are one of the following roles, you should follow the instructions:

For transaction signers: If you sign transactions with any 3rd party Substrate client which cannot deal with the runtime upgrade (i.e. subxt, GSRPC), you will need to restart or reload the client after the runtime upgrade applies. Otherwise you may get invalid signatures. Polkadot.js based clients should be able to automatically pick up the new metadata.

For index services: Please carefully examine the indexer after the runtime upgrade to make sure it operates properly.

Khala Network Runtime 1110-rc1

v0.1.11 Release Candidate 1

Khala Network Runtime 1100

The runtime 1100 contains the following major updates:

1. Introduce XCM pallets to enable HRMP channels
2. Update the bridge pallets to support assets routing
3. Update the upstream to polkadot-v0.9.15

Upgrade instructions

This upgrade is mainly an on-chain runtime upgrade. A new client is released and recommended to upgrade, but not required. Existing downstream consumers (including pherry and PRB), and all the clients relying on the recent version of polkadot.js can automatically handle the upgrade. It's suggested to keep monitoring the nodes to make sure they will operate normally.

However if you are one of the following roles, you should follow the instructions:

For transaction signers: If you sign transactions with any 3rd party Substrate client which cannot deal with the runtime upgrade (i.e. subxt, GSRPC), you will need to restart or reload the client after the runtime upgrade applies. Otherwise you may get invalid signatures. Polkadot.js based clients should be able to automatically pick up the new metadata.

For index services: Please carefully examine the indexer after the runtime upgrade to make sure it operates properly.

Khala Network Runtime 1091

The runtime 1091 is a minor upgrade to add back the missing storage migration for Council, TechnicalCommittee, Tips, and Bounties. To lean more about the storage migration, please check Phala-Network/phala-blockchain#612.

It also includes a minor typo fix in the pallet: Phala-Network/phala-blockchain@d782e8d

Upgrade instructions

This upgrade only contains an on-chain runtime upgrade. No new client is released. Existing downstream consumers including pherry and PRB, and all the clients relying on the recent version of polkadot.js can automatically handle the upgrade. It's suggested to keep monitoring the nodes to make sure they will operate normally.

However if you are one of the following roles, you should follow the instructions:

For transaction signers: If you sign transactions with any 3rd party Substrate client which cannot deal with the runtime upgrade (i.e. subxt, GSRPC), you will need to restart or reload the client after the runtime upgrade applies. Otherwise you may get invalid signatures. Polkadot.js based clients should be able to automatically pick up the new metadata.

For index services: Please carefully examine the indexer after the runtime upgrade to make sure it operates properly. This upgrade introduces a typo fix of PhalaMining.ExitUnresponsive. The indexer may be disturbed by the renaming.

Khala Network Runtime 1090

The new runtime version 1090 is a minor upgrade. It addresses the following problems:

• Upgrade to the upstream Substrate v0.9.13
• Prepare the backfill of Phala-Network/phala-blockchain#527
• Better event generation for indexers Phala-Network/phala-blockchain#592

Upgrade instructions

This upgrade is an on-chain runtime upgrade. The node client upgrade is high priority. It's not mandatory but highly recommended. The newer node can introduce some improvements on stability and performance.

For service providers that run a full node: If you run any 3rd party Substrate client which cannot deal with the runtime upgrade (i.e. subxt, GSRPC), you will need to restart the client after the runtime upgrade applies. Otherwise the newly signed transactions will have an invalid signature. Polkadot.js based clients should be able to automatically pick up the new metadata.

For solo miners: You will need to upgrade to the latest pherry docker image, because only the new version can connect to the runtime based on v0.9.13. Please strictly follow the follow step to upgrade:

1. Before the upgrade applies, keep the miner running
2. Once the runtime upgrade is applied, stop pherry
3. (Optionally but suggested) Stop the full node, and upgrade the full node docker image, and restart it
4. Upgrade the pherry docker image
5. Start pherry again

Please not that you don't need to stop or restart pruntime. For the instructions in detail, please read the solo mining wiki.

For Gatekeeper operators: Please follow the steps of the above solo miner.

For PRB cluster miners: You don't have to upgrade PRB. However an upgrade of both PRB and the full node is recommended.

Khala Network Runtime 1080 (Runtime only)

The new runtime version 1080 (runtime only, please don't update the client) is a minor upgrade which addressed the fixed point bug:

• Phala-Network/phala-blockchain#527

Bug Fixes and Improvements

• Phala-Network/phala-blockchain#566: Cap the removing stake by user locked amount

Khala Network Runtime 1070

The new runtime version 1070 (with khala-node v0.1.7) ships with the bridge_transfer extrinsic filter removed. It also introduces a bunch of bug fixes.

Features

• Enable Two-way Bridge

Bug Fixes and Improvements

• bridge-transfer: mark user call as transactional
• mining: add halving logic
• pallet: repair v again
• Less verbose handle_pool_new_reward

Khala Network Runtime 1060

The new runtime version 1060 (with khala-node v0.1.6) ships with the transfer extrinsic filter removed. It also removes the OneshotTransfer pallet, and introduces a bunch of bug fixes.

Features

• Enable Transfer

Bug Fixes

• Fix #490: limit 1 withdraw per user per queue
• Fix 518: Remove SubAccountAssignments
• Check worker status before start mining
• Fix #487: remove dust in stake & share calc
• gk: implement Repair V