Open Khala->Calamari HRMP - motion #91

- A message will be sent to Kusama to accept a request from Turing and open a channel.
- The message has a special code that tells Kusama what to do.
- Khala has enough money to open the channel.
- The channel will be used to send messages between Khala and Turing.
- The channel has a limit on how much can be sent and how big the messages can be.

Accept and open Khala<->Turing HRMP  - motion #88

Khala Runtime Upgrade v1150 - motion #89

Release some locked XCM PHA transfer from Karura (2) - motion #86

- There is a problem with Karura's app that caused two users' XCM transfer to get stuck.
- The XCMs were executed on Karura but not on Khala due to an incorrect weight issue.
- The assets are burnt on Karura but not distributed to the users on Khala.
- A motion is proposed to transfer the locked funds directly to the destination user using "balances.forceTransfer".
- A detailed user list can be found on the provided link.

Release some locked XCM PHA transfer from Karura - motion #84

Accept 2004 and 2111 swap on Kusama - motion #83

Update tokenomic parameter to match 15s block time - motion #78

Khala Runtime Upgrade v1140 - motion #79

Emergent chain data recovery - motion #76

Khala runtime upgrade v1131 and batch fixes - motion #75

Accept Moonriver->Khala HRMP channel - motion #70

Accept Parallel -> Khala HRMP (2nd try) - motion #67

- SubSquare is making some changes to a system called Khala.
- They need to move some tokens from one place to another to make sure everything is balanced.
- They need to mint some new tokens to make sure everything is fair.
- They are doing this so they can give people rewards for mining.
- This change is being made because they want to make sure everything is secure and fair.

Mint mining reward from bridge (2nd try) - motion #66

- Khala is going to connect with Moonriver using a one-way HRMP channel in 2023.
- This connection will be initiated through a batch call that includes two steps.
- The first step is to force the XCM version to 2023.
- The second step is to perform a transaction on Kusama with a specific call.
- Khala has enough deposit to open the channels.

Initiate Khala -> Moonriver HRMP  - motion #65

- Gemini launch is happening on April 8th.
- To get mining rewards, we need to transfer PHA tokens to Khala.
- We need to move tokens from Ethereum to the bridge and then to Khala.
- There was an imbalanced bridge, so we need to mint more tokens to balance it.
- A motion has been passed to mint tokens and transfer them to the mining reward pool account.

Mint mining reward from bridge - motion #63

- Khala is going to open a one-way channel called HRMP to Parallel in 2085.
- This will be done using a batch call that includes two steps.
- The transaction will be performed on Kusama using a specific code.
- This code will initiate the opening of the channel with specific parameters.
- Khala has enough money to open the channel.

Initiate Khala -> Parallel HRMP  - motion #59

Runtime Upgrade v1130 - Gemini update - motion #61

Runtime Upgrade v1120 - enable kUSD and fix XCM problems - motion #55

- A motion failed because it had the wrong number for the max capacity parameter.
- This motion fixes that mistake and changes "batchAll" to "batch".
- The motion will accept a request from Karura and ask them to open a two-way channel.
- There are three codes listed: proposal, embedded transact call, and decoded.
- The decoded code includes information about the recipient, proposed max capacity, and proposed max message size.

Open Karura-Khala HRMP channel (4) - motion #53

- This is a retry of a motion that failed before because of a weight issue.
- The motion will accept a request from Karura and send a request to open a two-way channel.
- There are some codes that are used to make this happen.
- The codes are decoded to show what they do.
- This will help Karura and the sender to communicate better.

Open Karura-Khala HRMP channel (3) - motion #52

- The motion is about accepting a request from Karura and opening a two-way channel.
- There was a previous try that didn't work because of some problems.
- The proposal includes some codes that will help to accept and open the channel.
- The codes are decoded to show what they will do.
- This is important for the Karura and Kusama communities to communicate and work together.

Open Karura-Khala HRMP channel (2) - motion #50

Runtime upgrade v1110 - motion #49

Accept Bifrost's HRMP request and open Khala->Bifrost channel (3nd try) - motion #45

SubSquare is trying to execute a motion called #41 on Kusama. They need at least 11 KSM to do this. They have provided some call data and call hash. They also have a transact on Kusama. The decoded transact is a utility.batchAll which includes hrmp.hrmpAcceptOpenChannel and hrmp.hrmpInitOpenChannel.

Accept Bifrost's HRMP request and open Khala->Bifrost channel (2nd try) - motion #43

SubSquare post content summary:

- The post contains some hexadecimal data and its decoded version.
- The hexadecimal data represents a transaction on Kusama.
- The decoded version shows that the transaction is related to opening a communication channel between two parties.
- The transaction includes some parameters such as sender, recipient, proposed maximum capacity, and maximum message size.
- The post also includes a hash value that represents the transaction.

Tech. Comm. Proposals