Releases: Phala-Network/khala-parachain
Khala Network Runtime 1181
Note that v1180 was withdrawn because we want to apply some upstream patches.
v1181 is a release with the following major changes:
- Add up to 8 council seats
- Allow
StakePoolManager
proxy to callPhalaStakePool.restart_mining
- Follow the upstream RMRK pallets
- Follow the upstream Polkadot v0.9.27, which is supposed to fix the state cache mismatch problem
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.
What's Changed
- Check destnation when extract from MultiLocation by @tolak in #158
- Upgrade to Polkadot 0.9.27 by @jasl in #159
- Allow StakePoolManager call pallet_stakepool.restart_mining by @jasl in #161
- Upgrade RMRK to latest commit, workaround PW for RMRK changes by @jasl in #164
- Some example code of new token transfer by @tolak in #166
- more event context information. by @Leechael in #167
- Pw updates fix compiling by @Leechael in #168
- Phala World Updates by @HashWarlock in #160
- Simplify property definition by @h4x3rotab in #171
- Upgrade to Polkadot 0.9.28 by @jasl in #172
- Add to 8 councillors by @h4x3rotab in #173
- Use Rust nightly-2022-09-08 by @jasl in #176
- Polkadot v0.9.29 by @jasl in #177
New Contributors
Full Changelog: v0.1.17...v0.1.18
Khala Network Runtime 1180
v1170 is a release with the following major changes:
- Add up to 8 council seats
- Allow
StakePoolManager
proxy to callPhalaStakePool.restart_mining
- Follow the upstream RMRK pallets
- Follow the upstream Polkadot v0.9.27, which is supposed to fix the state cache mismatch problem
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.
What's Changed
- Check destnation when extract from MultiLocation by @tolak in #158
- Upgrade to Polkadot 0.9.27 by @jasl in #159
- Allow StakePoolManager call pallet_stakepool.restart_mining by @jasl in #161
- Upgrade RMRK to latest commit, workaround PW for RMRK changes by @jasl in #164
- Some example code of new token transfer by @tolak in #166
- more event context information. by @Leechael in #167
- Pw updates fix compiling by @Leechael in #168
- Phala World Updates by @HashWarlock in #160
- Simplify property definition by @h4x3rotab in #171
- Upgrade to Polkadot 0.9.28 by @jasl in #172
- Add to 8 councillors by @h4x3rotab in #173
- Use Rust nightly-2022-09-08 by @jasl in #176
- Polkadot v0.9.29 by @jasl in #177
New Contributors
Full Changelog: v0.1.17...v0.1.18
Phala Network Runtime 1170
v1170 is a Phala Network runtime-only release for Khala upgrade.
What's Changed
- Phala World Updates by @HashWarlock in #156
- Add RMRK RPC & Scripts for Phala World Updates by @HashWarlock in #154
- Change desclen to 4400 by @Index0011 in #157
Full Changelog: v0.1.16.7...v0.1.17
Phala Network Runtime v1167
v1167 is a Phala Network runtime-only release.
What's Changed
- Enable fat contract on Thala by @jasl in #142
- Update Events by @HashWarlock in #143
- Add Calls for adding and accepting basic resources by @HashWarlock in #144
- Upgrade Rust to nightly-2022-07-11 by @jasl in #145
- Clean up warnings & add script for local testnet config for PhalaWorld by @HashWarlock in #147
- Upgrade to Polkadot 0.9.26 by @jasl in #146
- Upgrade JS dependencies by @jasl in #151
- chore: tune GH Actions again by @jasl in #149
- Move WrapSlice to new pallet-common by @tolak in #152
- Introduce ResourceId generation salt by @tolak in #148
Full Changelog: v0.1.16...v0.1.16.7
Khala Network Runtime 1160
The runtime 1160 contains the following updates:
- SubBridge minor improvements
- Misc improvements in StakePool (add events for indexer)
- Update the storage deposit of uniques pallet
- Update the upstream Substrate version to v0.9.24
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.
Phala Network Runtime 1151
The runtime 1151 is a minor update:
- Demacrocy functional
Khala Network Runtime 1150
The runtime 1150 contains the following major updates:
- Introduce NFTs: integrate
pallet-uniques
and Phala World pallets - Misc improvements in StakePool (separated reward claiming, and more events)
- Update the upstream Substrate version to v0.9.23
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 1140
The runtime 1140 contains the following major updates:
- Upgrade SubBridge to allow easy integration to 3rd party bridges and add BSX (Basilisk native token)
- Update the upstream Substrate version to v0.9.20
- Phala Pallets v6 migration: remove dirty data (
SubAccountAssignments
)
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.
For SubBridge frontend: The SubBridge related pallets are rewritten with the new API. The frontend interacting with SubBridge must specifically adapt the new API to ensure its functionalities. The XCM API is not changed. There's no action the other Parachains need to take.
Khala Network Runtime 1140-rc1
v0.1.14-rc1 release candidate 1 for v0.1.14
Khala Network Runtime 1131 (runtime only realse)
This is a minor bug-fix runtime only update. Changelog:
- Allow to stake by replacing the withdrawing queue without enough remaining cap (Phala-Network/phala-blockchain#693)
- Trigger the fix to unresponsive worker reward (Phala-Network/phala-blockchain#738)