<p>In order to alow TEER to be transferred to Asset Hub Kusama by anyone, we need KSM as an asset on our chain because XCM fees for Asset Hub need to be paid in KSM<br /><br />Noteworthy is the asset controller: it is a non-account. A simple string with no private key. This equals having no asset controller at all, which is desired. Only root origin can make changes to this asset</p>

In order to alow TEER to be transferred to Asset Hub Kusama by anyone, we need KSM as an asset on our chain because XCM fees for Asset Hub need to be paid in KSM  
  
Noteworthy is the asset controller: it is a non-account. A simple string with no private key. This equals having no asset controller at all, which is desired. Only root origin can make changes to this asset

- Problem Statement: TEER transfer to Asset Hub Kusama requires KSM on the chain for XCM fees, with the asset controller being a non-account.
- Significance: Ensuring seamless TEER transfers to Asset Hub Kusama and simplifying asset controller management.
- Proposed Solution: Incorporating KSM as an asset on the chain with a non-account asset controller.
- Expected Outcomes: Streamlined TEER transfers, improved asset controller management, and enhanced functionality for users.

Register KSM asset on Integritee Network

No Active Proposals