update:&nbsp;
"Antonio Antonino" pointed out that I should use <code>establishChannelWithSystem(targetSystemChain)</code> to automatically establish a bi-directional channel with AssetHub. Therefore abandoning this proposal. But he suggested waiting for the next Kilt runtime (in a few weeks) before reproposing.
------------------- title:&nbsp;Initiate opening XCM/HRMP channel with AssetHub
Opening an XCM channel (bidirectional HRMP channels) requires three steps:
<ol>
<li>Kilt initiates opening an HRMP channel from Kilt -&gt; AssetHub</li>
<li>AssetHub accepts the channel and initiates opening a channel back to Kilt</li>
<li>Kilt accepts the return HRMP channel from AssetHub -&gt; Kilt</li>
</ol>
This proposal will accomplish Step 1. Previously, Step 2 would require a Polkadot referendum to accept the HRMP channel on behalf of AssetHub, but recently system chains were configured to auto-accept channels.
Note that Kilt did not previously have enough DOT in its child account on the Polkadot relaychain to open more channels. However, with the execution and payout of <a href="https://polkadot.subsquare.io/referenda/1071">Polkadot referendum 1071</a>&nbsp;yesterday, Kilt now has <a href="https://polkadot.subscan.io/account/13YMK2dxjYEL7c6ymsM996UcwK3xBnKQmSxKx6DNEwsVoSQg">205 DOT in its account</a> so a total of 10 XCM channels can be opened.&nbsp;
This channel with AssetHub was what one Kilt dev told me they had been working on integration testing for, so we'll start with AH. This proposal took 2hrs to craft, test, and submit.

vote Nay. Wait until next runtime upgrade

It is time for KILT to join Polkadot DeFi and integrate with other chains. But first that means opening up more XCM channels to interact with other parachains. And for each XCM channel you open, you need 20 DOT (10 DOT for each HRMP direction) in the [Kilt child account on Polkadot](https://polkadot.subscan.io/account/5Ec4AhNtskxrg56TpEJ8zweU5h4JVUmGgxDqnoE1grqycu6q). Currently Kilt's child account has 25 DOT, with 5 DOT transferable (20 DOT locked for the XCM channel with Hydration).

I propose opening XCM channels with the following chains:
- AssetHub - enable CEX transfers of KILT
- Interlay - open KILT money market for lending and borrowing
- Polkadex - list KILT on their perp orderbook (8 AYE votes in [Kilt discussion 235](https://kilt.polkassembly.network/post/235))
- Moonbeam, Astar - make KILT available for EVM DeFi


That's five channels immediately, which would require 5x20=100 DOT. The next chains that KILT might want to connect to are:
- Centrifuge requires KYC for investors. Maybe they want to integrate DID?
- Mythical just launched their chain today. Maybe they'd want to integrate optional DID somehow?
- Polimec - Kilt DID already being used for public sale KYC. XCM channel not required for DIP, but maybe KILT token could be used to pay KYC fees? (more use cases for KILT)

It'd probably be good to put 240-300 DOT into the child account to be ready for any other XCM channel requests in the future. But the [KILT treasury](https://spiritnet.subscan.io/account/4qPZ8fv6BjGoGKzfx5LtBFnEUp2b5Q5C1ErrjBNGmoFTLNHG) holds 4M KILT and no DOT. Does the KILT team have a separate account that they could use to fund the Kilt child account with? If not, the other option is to execute an XCM transaction from Kilt governance to transfer 9333 KILT to Hydration, swap KILT for 300 DOT, and then transfer the 300 DOT to the Kilt child account on Polkadot.

This is the series of on-chain referenda to accomplish the goals above:
1. XCM transfer 9333 KILT from KILT treasury to KILT sibling acct on Hydration. Set KILT as transaction fee currency. Buy 300 DOT with KILT.
2. XCM transfer 300 DOT from KILT sibling acct on Hydration to the KILT child acct on Polkadot. (NOTE: could be combined with #1 but price fluctuation might affect how much DOT is bought)
3. Initiate opening HRMP channels to AssetHub, Moonbeam, Astar, Polkadex (and Centrifuge, Mythical, Polimec?)
4. Accept incoming HRMP channels from Interlay and Bifrost.
(referenda on other chains to accept Kilt incoming channel and send one back)
5. Additional referenda to accept HRMP channels sent back from other chains.

I discussed with Antonio Antonio yesterday in TG, and he was concerned about unforseen risks of opening XCM channels without lots of integration unit tests first. While I love adding more automated tests to ensure things are correctly configured ([maybe here?](https://github.com/open-web3-stack/polkadot-ecosystem-tests/blob/master/packages/polkadot/src/acala.polkadot.test.ts)), so far community consensus is that XCM channels themselves pose negligible risk to parachain security. At a minimum, Kilt will need to perform referenda #1 and #2 above in order to open the AssetHub XCM channel that Antonio does already have thorough automated tests for.