This motion will trigger the runtime upgrade for Khala Network Runtime v1241. It is a bug fix for the WrappedBalances pallet.

For details, please check [here](https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.24-khala-runtime-1241)

Khala Runtime Upgrade v1241 - motion #196

This motion will trigger the runtime upgrade for Khala Network Runtime v1230. It is a new Khala runtime and client release with the following features:

- Add inDEX pallet
- Prepare for Phala Compute & Phat Contract launch
- Upgrade upstream substrate (Polkadot v0.9.40) with database stability improvements

For details, please check [here](https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.23)

Khala Runtime Upgrade v1230 - motion #195

This is a retry of the [motion #188](https://khala.subsquare.io/council/motion/188).

The original motion was not executed successfully because the permission was set incorrectly. It requires root permission to execute. So in this motion, we are going to execute the same steps but in a referenum.

## Original proposal

This motion is a batch call to fix the ChainBridge migration issue on ZLK after we upgrade to XCM v3.
With the new XCM version, `GeneralKey` definition was changed, which influence our resource id
and reserve account calculation on ChainBridge. The batch contains 6 calls:

1. Call-1 set ZLK to a temporary location `(1, X2(Parachain(2001), GeneralIndex(0))`
2. Call-2 set ZLK back to its real location `(1, X2(Parachain(2001), GeneralKey(2, 0x0207..00))`
The above two call will trigger ZLK resource id updated to proper value automatically
3. Call-3 force burn `196247848001219224432700` units ZLK from old reserve account(pub key): `0xde50ca45c8f7323ea372fd5d7929b9f37946690b0b668985beebe60431badcea`
4. Call-4 force mint `196247848001219224432700` units ZLK to new reserve account(pub key): `0x95f793efdd6b1f7894f6c4d9bcb3de87d4e58385c56ebf1bfef91f9ab2144b91`
5. Call-5 force burn `2026420000000000000000` units ZLK from temporary account: `427Xv1Y1bNNQ5XU6pCCVGbqTgEe41t6s4GAYCCCDwASWsXpa`
5. Call-6 force mint `2026420000000000000000` units LK to external account: `43L9xU7zKU2ByNKvsgb4QLnhBU4pVvfbphh52TeH8byRtPuj`

There are 5 transaction that have their ZLK locked in the temporary account: 
<https://khala.subscan.io/event?address=427Xv1Y1bNNQ5XU6pCCVGbqTgEe41t6s4GAYCCCDwASWsXpa&module=assets&event=issued&startDate=&endDate=&startBlock=&endBlock=&timeType=date&version=1220>

And the external account will bridge ZLK to user account on Moonriver



Fix ChainBridge migration for ZLK (2nd try) - motion #190

This motion will trigger the runtime upgrade for Khala Network Runtime v1210. It is a new Khala runtime release with the following features:

- Bug fixes in Stake Pool v2 and Vault
- Bug fixes in RMRK Marketplace
- Upgrade upstream substrate (Polkadot v0.9.39) with database stability improvements

For details, please check [here](https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.21)

Khala Runtime Upgrade v1210 - motion #187

The Phala team has successfully secured the Kusama parachain 2264 to extend the leasing period of Khala Network. In this motion, it will trigger a Transact message on Kusama to pair the swap request sent from 2264.

The transact will be performed on Kusama with the following call:

```
0x4603d4070000d8080000
```

which can be decoded as:

```
registrar.swap(
  id: 2,004,
    other: 2264,
)
```

Khala's sovereign account has already got enough deposit to do swap.

Swap Khala parachain slot with parachain 2264 - motion #186

This motion will try to re-execute:

- [Motion 178](https://khala.subsquare.io/council/motion/178), which was succeeded and fast-tracked but the external proposal was not voted in time.
- [Motion 177](https://khala.subsquare.io/council/motion/176), which was succeeded but the transact weight limit is too low.
- [Motion 176](https://khala.subsquare.io/council/motion/176), which was succeeded but the external proposal was overwritten.
- [Motion 174](https://khala.subsquare.io/council/motion/174), which was failed because it should be a external referendum instead of a simple motion.

## Original proposal

This motion will trigger a Transact message on Kusama to accept&send the HRMP request sent from Litmus Network.

The transact will be performed on Polkadot with the following call:

```
0x1802083c013a0800003c003a080000e803000000900100
```

which can be decoded as:

```
hrmp.hrmpAcceptOpenChannel(
  sender: 2,106,
)
hrmp.hrmpInitOpenChannel(
  recipient: 2,106,
  proposedMaxCapacity: 1,000
  proposedMaxMessageSize: 102,400
)
```

Khala's sovereign account has already got enough deposit to open the channels

Accept & Open HRMP channel with Litmus (5th try, sadly) - motion #180

This motion will trigger the v1210 runtime upgrade with the following features:

- Fix a dead-loop problem in Stake Pool withdraw
- Enable PhalaWorld marketplace
- Upgrade upstream Substrate to v0.9.37

For more details, please refer to: <https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.21>

Khala Runtime Upgrade v1210 - motion #181

This motion will try to re-execute:

- [Motion 177](https://khala.subsquare.io/council/motion/176), which was succeeded but the transact weight limit is too low.
- [Motion 176](https://khala.subsquare.io/council/motion/176), which was succeeded but the external proposal was overwritten.
- [Motion 174](https://khala.subsquare.io/council/motion/174), which was failed because it should be a external referendum instead of a simple motion.

## Original proposal

This motion will trigger a Transact message on Kusama to accept&send the HRMP request sent from Litmus Network.

The transact will be performed on Polkadot with the following call:

```
0x1802083c013a0800003c003a080000e803000000900100
```

which can be decoded as:

```
hrmp.hrmpAcceptOpenChannel(
  sender: 2,106,
)
hrmp.hrmpInitOpenChannel(
  recipient: 2,106,
  proposedMaxCapacity: 1,000
  proposedMaxMessageSize: 102,400
)
```

Khala's sovereign account has already got enough deposit to open the channels

Accept & Open HRMP channel with Litmus (4th try) - motion #178

This motion will try to re-execute:

- [Motion 176](https://khala.subsquare.io/council/motion/176), which was succeeded but the external proposal was overwritten.
- [Motion 174](https://khala.subsquare.io/council/motion/174), which was failed because it should be a external referendum instead of a simple motion.

## Original proposal

This motion will trigger a Transact message on Kusama to accept&send the HRMP request sent from Litmus Network.

The transact will be performed on Polkadot with the following call:

```
0x1802083c013a0800003c003a080000e803000000900100
```

which can be decoded as:

```
hrmp.hrmpAcceptOpenChannel(
  sender: 2,106,
)
hrmp.hrmpInitOpenChannel(
  recipient: 2,106,
  proposedMaxCapacity: 1,000
  proposedMaxMessageSize: 102,400
)
```

Khala's sovereign account has already got enough deposit to open the channels

Accept & Open HRMP channel with Litmus (3rd try) - motion #177

The compute reward subsidy pool has only 7M left (around 1 month of the reward). This motion is a part of the effort to unlock 155M PHA (around 1 year budget) and move it as the Khala reward. Since the unlock is 155M PHA. The SubBridge reservation accounts on both Khala and Phala should add 155M to the locked account. Then the locked balance on Ethereum can be moved to Khala via bridge transfer.

This motion will mint 155M PHA on a temporary account on **Khala**, and transfer it to the bridge reservation account via a batchAll call. The temporary account is `43RZEPV1f652dRS9d6xxpnEfo74ndNAcZ2qk4yU9qbegCTmZ`, which is randomly generated.


Mint 155M PHA for the unlocking compute reward - motion #175

This motion will trigger the v1208 runtime upgrade for bug fixes:

- Storage performance fix for StakePool v2 upgrade
- Loosen condition check for confidence level 2 to reflect the Intel definition more accurately

For more details, please refer to: <https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.20-khala-runtime-1208>

Khala Runtime Upgrade v1208 - motion #172

This motion will trigger the v1207 runtime upgrade for bug fixes:

- Fix the dust problem preventing contribute & withdraw in pools

For more details, please refer to: <https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.20-khala-runtime-1207>

Khala Runtime Upgrade v1207 - motion #165

This motion will trigger the v1206 runtime upgrade for bug fixes:

- StakePool claimable reward migration backfill
- RMRK storage leakage mitigation & backfill

For more details, please refer to: <https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.20-khala-runtime-1206>

Khala Runtime Upgrade v1206 - motion #163

This motion will trigger the v1205 runtime upgrade for bug fixes:

- Fix Vault amount overflow problem & backfill methods
- PhalaWorld fixes & migration

For more details, please refer to: <https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.20-khala-runtime-1205>

Khala Runtime Upgrade v1205 - motion #161

This motion will trigger the v1204 runtime upgrade for bug fixes. For more details, please refer to: <https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.20-khala-runtime-1204>

Khala Runtime Upgrade v1204 - motion #160

This motion will trigger an external referendum to runtime to v1202 to facilitate the runtime migration. 

For more details about Runtime v1202, please refer to the [Github release page](https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.20-khala-runtime-1202).

Runtime 1202 & Prepare for StakePool v2 launch (7) - motion #156

This motion will trigger an external referendum to runtime to v1201 to facilitate the runtime migration. Major changes:

- Enable StakePool v2 and Vault basic filter
- Remove migrations

For more details about Runtime v1200, please refer to the [Github release page](https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.19-9-runtime-1200).

Runtime 1201 & Prepare for StakePool v2 launch (4) - motion #153

This motion will trigger an external referendum to runtime to v1200 to facilitate the runtime migration. 

For more details about Runtime v1200, please refer to the [Github release page](https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.19-9-runtime-1200).

Runtime 1200 & Prepare for StakePool v2 launch (3) - motion #152

This motion will trigger an external referendum to runtime to v1199. Once the upgrade is triggered, the StakePool v2 multi-block migration will start.

Runtime 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

For more details about Runtime v1199, please refer to the [Github release page](https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.19-9).

----

This motion is a part of the StakePool v2 launch plan, which passed the vote on [Referenda #67](https://khala.subsquare.io/democracy/referendum/67)

Runtime 1199 & Prepare for StakePool v2 launch (2) - motion #151

This motion will trigger an external referendum to do the following things:

1. Pause heartbeat. It's required to pause the tokenomic and mining mechanism before the StakePool v2 upgrade.
2. Set the Wrapped PHA token metadata (Symbol: wPHA, ID: 10000)

This motion is a part of the StakePool v2 launch plan, which passed the vote on [Referenda #67](https://khala.subsquare.io/democracy/referendum/67)

Prepare for StakePool v2 launch (1) - motion #148

This motion will register W-PHA (Wrapped PHA) on Khala for StakePool v2 preparation. It will also trigger the registering of pruntime v0.2.5 on Khala again, because the last launch motion missed one vote (5 vote at least, given it's "greater than half of the council or root").

---

Origin proposal of Motion #143:

This motion will whitelist pruntime v0.2.5 on Khala. This version introduces a fix on the Grandpa justification validation problem described [here](https://forum.phala.network/t/topic/3701).

Related PR: <https://github.com/Phala-Network/phala-blockchain/pull/1034>

Register WPHA assets and launch pruntime v0.2.5 again - motion #146

This motion is a batch call to (1) register the following assets and set each execution price to 80_000_000_000_000_000_000, and (2) trigger a Transact message on Kusama to open a HRMP request to Pioneer Network.

Registering:

1. Pioneer NEER: id=13, path="../Parachain(2096)/GeneralKey(0x000000000000000000)", sym=NEER, dec=18
2. Pioneer BIT: id=14, path="../Parachain(2096)/GeneralKey(0x020000000000000000)", sym=BIT, dec=18

Transact:

**0x3c0030080000e803000000900100**

which can be decoded as:

```
hrmp.hrmpInitOpenChannel(
  recipient: 2,096
  proposedMaxCapacity: 1,000
  proposedMaxMessageSize: 102,400
)
```

Khala's sovereign account has already got the enough deposit to open the channels.

Register XCM assets & Open Khala -> Pioneer Network HRMP - motion #144

v1192 is a release with the following changes:

- Introduce PhalaWorld incubation logic

For more details, please check: <https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.19-2.1>

Khala Network Runtime 1192 - motion #142

v1191 is a release with the following changes:

- Prepare for StakePool v2 migration: forbid remove_worker before reclaiming

For more details, please check: <https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.19-1.1>

Khala Network Runtime 1191 - motion #140

v1190 is a release with the following changes:

* PhalaWorld feature updates
* Update to Polkadot 0.9.30

For more details, please check: <https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.19>

Democracy Referenda