This is a follow up of [motion #54](https://khala.subsquare.io/council/motions). In the last motion, we failed to register the remote assets on Khala because the permission control was incorrect. Therefore we have upgraded the runtime to v1120 with the fix to the problem.

In this motion, we try to add the remote assets again:

1. Register parachain asset 0: KSM (Kusama's native token) at ".."
2. Register parachain asset 1: KAR (Karura's native token) at "../2000/0x0080"
3. Register parachain asset 2: BNC (Bifrost's native token) at "../2001/0x0001"
4. Register parachain asset 3: ZLK (Zenlink token on Bifrost) at "../2001/0x0207"
5. Register parachain asset 4: kUSD (kUSD on Karura) at "../2000/0x0081"
6. Enable ChainBridge on chain 2 (Moonriver) for XCM asset 3 (ZLK)

SubSquare is trying to add remote assets to Khala and has upgraded the runtime to fix a previous problem. Here are the assets they are trying to add:

1. KSM (Kusama's native token)
2. KAR (Karura's native token)
3. BNC (Bifrost's native token)
4. ZLK (Zenlink token on Bifrost)
5. kUSD (kUSD on Karura)

They also want to enable ChainBridge on chain 2 (Moonriver) for ZLK.

#56·Config SubBridge again - motion #56