Skip to content

Releases: Phala-Network/khala-parachain

Khala Network Runtime 1181

23 Sep 04:24
Compare
Choose a tag to compare

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 call PhalaStakePool.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

New Contributors

Full Changelog: v0.1.17...v0.1.18

Khala Network Runtime 1180

20 Sep 12:16
Compare
Choose a tag to compare

v1170 is a release with the following major changes:

  • Add up to 8 council seats
  • Allow StakePoolManager proxy to call PhalaStakePool.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

New Contributors

Full Changelog: v0.1.17...v0.1.18

Phala Network Runtime 1170

11 Aug 07:34
cc5ae58
Compare
Choose a tag to compare

v1170 is a Phala Network runtime-only release for Khala upgrade.

What's Changed

Full Changelog: v0.1.16.7...v0.1.17

Phala Network Runtime v1167

29 Jul 16:04
5c3a794
Compare
Choose a tag to compare

v1167 is a Phala Network runtime-only release.

What's Changed

Full Changelog: v0.1.16...v0.1.16.7

Khala Network Runtime 1160

22 Jun 14:00
82d9a95
Compare
Choose a tag to compare

The runtime 1160 contains the following updates:

  1. SubBridge minor improvements
  2. Misc improvements in StakePool (add events for indexer)
  3. Update the storage deposit of uniques pallet
  4. 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

14 Jun 12:39
Compare
Choose a tag to compare

The runtime 1151 is a minor update:

  • Demacrocy functional

Khala Network Runtime 1150

09 Jun 08:03
Compare
Choose a tag to compare

The runtime 1150 contains the following major updates:

  1. Introduce NFTs: integrate pallet-uniques and Phala World pallets
  2. Misc improvements in StakePool (separated reward claiming, and more events)
  3. 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

12 May 10:04
12d76b5
Compare
Choose a tag to compare

The runtime 1140 contains the following major updates:

  1. Upgrade SubBridge to allow easy integration to 3rd party bridges and add BSX (Basilisk native token)
  2. Update the upstream Substrate version to v0.9.20
  3. 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

12 May 10:04
be54212
Compare
Choose a tag to compare
Pre-release
v0.1.14-rc1

release candidate 1 for v0.1.14

Khala Network Runtime 1131 (runtime only realse)

29 Apr 15:50
Compare
Choose a tag to compare

This is a minor bug-fix runtime only update. Changelog:

  1. Allow to stake by replacing the withdrawing queue without enough remaining cap (Phala-Network/phala-blockchain#693)
  2. Trigger the fix to unresponsive worker reward (Phala-Network/phala-blockchain#738)