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.

update: 

"Antonio Antonino" pointed out that I should use `establishChannelWithSystem(targetSystemChain)` 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: Initiate opening XCM/HRMP channel with AssetHub

Opening an XCM channel (bidirectional HRMP channels) requires three steps:

1.  Kilt initiates opening an HRMP channel from Kilt -> AssetHub
2.  AssetHub accepts the channel and initiates opening a channel back to Kilt
3.  Kilt accepts the return HRMP channel from AssetHub -> Kilt

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 [Polkadot referendum 1071](https://polkadot.subsquare.io/referenda/1071) yesterday, Kilt now has [205 DOT in its account](https://polkadot.subscan.io/account/13YMK2dxjYEL7c6ymsM996UcwK3xBnKQmSxKx6DNEwsVoSQg) so a total of 10 XCM channels can be opened. 

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.

- **Problem Statement:** 
  - Need to establish a bi-directional XCM/HRMP channel with AssetHub.

- **Significance:** 
  - Previously required a Polkadot referendum for AssetHub to accept the channel, now auto-acceptance is possible.
  - Kilt now has enough DOT to open 10 XCM channels after Polkadot referendum 1071.

- **Proposed Solution:** 
  - Initiate opening an HRMP channel from Kilt to AssetHub.

- **Expected Outcomes:** 
  - Ability to establish a bi-directional XCM/HRMP channel with AssetHub.

vote Nay. Wait until next runtime upgrade

No Active Proposals