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 Polkadot to receive&open a HRMP request to Bifrost Network.

Registering:

1. Bifrost BNC: id=8, path="../Parachain(2030)/GeneralKey(0x0104)", sym=BNC, dec=12

Transact:

**0x1a02083c01ee0700003c00ee070000e803000000900100**

which can be decoded as:

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

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

proposalHash

votingPeriod

delay

Register XCM assets & Receive&Open Phala -> Bifrost Network HRMP - motion #22

This motion will trigger a Transact message on Polkadot to accept the HRMP request sent from Astar Network.

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

```
0x3c01d6070000
```

which can be decoded as:

```
hrmp.hrmpAcceptOpenChannel(
  sender: 2,006,
)
```

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

Accept Astar -> Phala Network Open HRMP Request - motion #21

This motion will trigger a Transact message on Polkadot to Receive a HRMP request from Darwinia Network.

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

```
0x3c01fe070000
```

which can be decoded as:

```
hrmp.hrmpAcceptOpenChannel(
  recipient: 2,046
)
```

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

Accept Darwinia -> Phala Network HRMP - motion #19

This is a retry of [Motion #17](https://phala.subsquare.io/council/motion/1056321_0x0f8e0e3a28d139b1beaf4361a7ebb19e8c7e27b3d5863ec857c0c56d2e94ef2c). The motion 17 was canceled because the specified max transaction fee was 100x larger since it used an incorrect decimal number. This motion fixes it.

## Original motion

This motion will trigger a Transact message on Polkadot to open a HRMP request to Crab Network.

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

```
0x3c00d6070000e803000000900100
```

which can be decoded as:

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

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

Open Phala -> AStar Network HRMP - motion #18

This motion will trigger a Transact message on Polkadot to open a HRMP request to Darwinia Network.

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

```
0x3c00fe070000e803000000900100
```

which can be decoded as:

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

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

Open Phala -> Darwinia Network HRMP (2nd try) - motion #16


This motion will trigger a Transact message on Polkadot to open a HRMP request to Statemint Network.

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

```
0x3c00e8030000e803000000900100
```

which can be decoded as:

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

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

Open Phala -> Statemint Network HRMP - motion #14

This motion will transfer 16172545078129820115 pico PHA from the crowdloan reward temporary account `42fy3tTMPbgxbRqkQCyvLoSoPHwUPM3Dy5iqHYhF9RvD5XAP` to account `5EYCAe5g8L4VTWvgypDb7EwVVCUjn5rpsrL4YsbAoLXSXuE7` which is drived by pallet id `crow/tmp` . Then burn it from the the latter, the latter account balance should be zero after burn.

This motion will balance the PHA supply on Phala Network. 38M PHA was bridged from crowdloan reward account on Ethereum to Phala. Considering there already have 16172545078129820115 pico PHA in circulation when Phala was initially launched, we should burn the redundant amount of PHA.

At the [Motion 9](https://phala.subsquare.io/democracy/external/611149_0x5f08313df9249e8ae126dd3536aa6e7a3f6724e02c9a9d88f7fb3e4d33ad9c8e), we have discussed why we need to burn the token.

Burn redundant PHA to balance the blockchain supply - motion #13

This motion will trigger a Transact message on Polkadot to accept a HRMP request from Moonbeam Network.

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

```
0x3c01d4070000
```

which can be decoded as:

```
hrmp.hrmpAcceptOpenChannel(
  sender: 2004
)
```


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


Accept Moonbeam -> Phala Network HRMP - motion #12

This motion will trigger a Transact message on Polkadot to accept a HRMP request from Parallel Network.

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

```
0x3c01dc070000
```

which can be decoded as:

```
hrmp.hrmpAcceptOpenChannel(
  recipient: 2,012
)
```

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

Accept Parallel -> Phala Network HRMP - motion #10

This is a retry of Motion #6, because we forgot to vote in its Fast-Track period and it failed.

## Original proposal

As discussed in the [companion motion](https://khala.subsquare.io/council/motion/2108614_0x78b0395a972c69912d6c144cec2dcc8721fc16a3b3f0e2c5883e09041c469e5d) on Khala, we need to mint reservation funds to launch SubBridge.

This motion will mint 536.8M PHA to the SubBridge reservation account (436H4jat7TobTbNX4RCH5p7qgErHbGTo1MyZhLVaSX4FkKyz, `modlphala/bg`), and enable three relayers to bridge PHA to Ethereum.

536.8M PHA is calculated by (1B - 463.2M), where 463.2M is the locked mining subsidy reward on Ethereum. For detailed explanation, please refer to the Khala motion.

There are ~16.172 M PHA supply on Phala, which should come from the Phala crowdloan reward reservation (on Ethereum), and team operation funds. So after 536.8M is minted, we are going to transfer the full crowdloan reservation to Phala and burn the amount of the actual crowdloan reward distribution. And transfer the other funds from the team wallet to Phala, and burn the corresponding amount. Finally, the full redundant 16.172M PHA will be burned. The total supply on Phala should be exactly 536.8M PHA.

There will be follow up operations to balance the supply.

Retry: Mint reserved funds for Phala SubBridge launch - motion #9

This motion will trigger a Transact message on Polkadot to open a HRMP request to Parallel Network.

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

```
0x3c00dc070000e803000000900100
```

which can be decoded as:

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

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

Open Phala -> Parallel HRMP - motion #8

As discussed in the [companion motion](https://khala.subsquare.io/council/motion/2108614_0x78b0395a972c69912d6c144cec2dcc8721fc16a3b3f0e2c5883e09041c469e5d) on Khala, we need to mint reservation funds to launch SubBridge.

This motion will mint 536.8M PHA to the SubBridge reservation account (436H4jat7TobTbNX4RCH5p7qgErHbGTo1MyZhLVaSX4FkKyz, `modlphala/bg`), and enable three relayers to bridge PHA to Ethereum.

536.8M PHA is calculated by (1B - 463.2M), where 463.2M is the locked mining subsidy reward on Ethereum. For detailed explanation, please refer to the Khala motion.

There are ~16.172 M PHA supply on Phala, which should come from the Phala crowdloan reward reservation (on Ethereum), and team operation funds. So after 536.8M is minted, we are going to transfer the full crowdloan reservation to Phala and burn the amount of the actual crowdloan reward distribution. And transfer the other funds from the team wallet to Phala, and burn the corresponding amount. Finally, the full redundant 16.172M PHA will be burned. The total supply on Phala should be exactly 536.8M PHA.

There will be follow up operations to balance the supply.

Mint reserved funds for Phala SubBridge launch - motion #6

Unfortunately, we made the same mistake as we did on Khala -- we forgot to set the safe XCM version. As a result, the previous motion to open HRMP channels was failed.

In this motion, we submit the external proposal again with some changes:

1. Add `polkadotXcm.forceDefaultXcmVersion(2)` before sending the XCM to Polkadot
2. Accept Acala's HRMP request
3. Send a HRMP request to Acala
4. Send a HRMP request to Moonbeam
5. Additionally open a new HRMP channel request to Parallel parachain

Raw transact call: `0x1a04103c01d00700003c00d0070000e8030000009001003c00d4070000e8030000009001003c00dc070000e803000000900100`

Retry Motion 3 (open HRMP channels) - motion #5

This motion will send a Transact to do the following things:

1. Accept Acala's HRMP request
2. Send a HRMP request to Acala
3. Send a HRMP request to Moonbeam

Raw transact call: `0x1a000c3c01d00700003c00d0070000e8030000009001003c00d4070000e803000000900100`

Open HRMP channels with Acala & Moonbeam - motion #3

Runtime upgrade v1167 is required to enable SubBridge. For more details, please check:

<https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.16.7>