Khala Network Runtime v1204

Improvements:

• Auto remove pool NFT properties when burnt
• A function to manually clean up the legacy properties

What's Changed

• Sync phala for rmrk problem by @jasl in #240
• Sync phala for rmrk problem 2 by @jasl in #241

Full Changelog: v0.1.20-khala-runtime-1202...v0.1.20-khala-runtime-1204

Khala Network Runtime v1202

Khala Network Runtime v1202 is a part of the Stake Pool v2 upgrade migration.

• Add stake lock backfill
• Change Stake Pool withdraw grace period back to 7 days
• Fix "newly created account cannot unwrap" issue

What's Changed

• change cooldown period by @Index0011 in #237
• Sync Phala changes to c83ee94, fix unwrap and lock_account by @jasl in #239

Full Changelog: v0.1.20...v0.1.20-khala-runtime-1202

Khala Network Runtime v1201

Khala Network Runtime v1201 is a part of the Stake Pool v2 upgrade migration.

• Enable StakePool v2 and Vault basic filter
• Remove migrations

What's Changed

• Update to release 1201 by @Index0011 in #229
• Bump to v0.1.20, spec version 1200 (Khala 1201) by @jasl in #234
• Remove staled Phala pallets migrations by @jasl in #235

Full Changelog: v0.1.19-9-runtime-1200...v0.1.20

Khala Network Runtime v1200

Khala Network Runtime v1200 is a part of the Stake Pool v2 upgrade migration.

Khala Network Runtime 1199

v1199 is a major runtime release with the following changes:

• Stake Pool v2 & Vault: completely redesigned Phala Compute
• Multi-block migrations
• Follow the upstream substrate v0.9.33

In this runtime, the compute components are disabled for migration. There will be a follow up upgrade to fully enable them.

Upgrade instructions

This upgrade is an on-chain runtime upgrade with major breaking changes. pherry 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 PRB users: You must upgrade PRB to the latest version (will release soon; once release, we will update the description here) before the next runtime upgrade. Otherwise the managed workers may not work properly.
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

• Fix code comment. Method called by Overlord by @kureus in #219
• post migration by @Index0011 in #221
• push by @Index0011 in #222
• Add initial migration implementation for updates from RMRK. by @HashWarlock in #216
• Upgrade to Polkadot v0.9.33 (from 0.9.30) by @jasl in #215
• push by @Index0011 in #225
• Polkadot v0.9.33 1 by @Index0011 in #226

New Contributors

• @kureus made their first contribution in #219

Full Changelog: v0.1.19-2.1...v0.1.19-9

Khala Network Runtime 1192

v1192 is a runtime-only release with the following changes:

• Introduce PhalaWorld incubation logic

Upgrade instructions

This upgrade is mainly an on-chain runtime upgrade. 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

• Add Signer Account by @HashWarlock in #198
• Update Incubation Feeding Logic by @HashWarlock in #195
• Bump to v0.1.19-2 and runtime 1192 by @jasl in #204
• Port Phala PR #1046 & #1047 by @jasl in #206

Full Changelog: v0.1.19-1.1...v0.1.19-2.1

Khala Network Runtime 1191-1

v1191 is a runtime-only release with the following changes:

• Prepare for StakePool v2 migration: forbid remove_worker before reclaiming

Upgrade instructions

This upgrade is mainly an on-chain runtime upgrade. 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

• Scripts for PhalaWorld by @Leechael in #192
• Restrict remove_worker limitation by @Index0011 in #196

Full Changelog: v0.1.19...v0.1.19-1.1

Khala Network Runtime 1190

v1190 is a release with the following changes:

• PhalaWorld feature updates
• Update to Polkadot 0.9.30

Upgrade instructions

This upgrade is mainly an on-chain runtime upgrade. 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

• Update incubation PartInfo with metadata database update by @Leechael in #186
• Upgrade to Polkadot 0.9.30 by @jasl in #187
• Expand to 8 councillors for Phala by @jasl in #189
• Automating Test Chain State Scripts & Increase Test Coverage Scenarios by @HashWarlock in #184
• Phala World Shell Parts & Market Updates by @HashWarlock in #182
• Update dev scripts by @h4x3rotab in #190
• Add Payee Multi-Sig Account and Royalties by @HashWarlock in #191

Full Changelog: v0.1.18-3...v0.1.19

Khala Network Runtime 1183

v1183 is a runtime-only release with the following changes:

• Add events for StakePool indexing

Upgrade instructions

This upgrade is mainly an on-chain runtime upgrade. 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.

Full Changelog: v0.1.18-2...v0.1.18-3

Khala Network Runtime 1182

v1182 is a runtime-only release with the following major changes:

• Fix utility.batch* None permission check
• Add event arguments to the mining pallet

Upgrade instructions

This upgrade is mainly an on-chain runtime upgrade. 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

• Fix utility.batch* None permission check
• Add event arguments to the mining pallet

Full Changelog: v0.1.18-1...v0.1.18-2