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
<a href="38">Ref 38</a> attempting the same had failed because: 
<ol>
<li>the asset owner account did not exist</li>
<li>we used `Raw` instead of `Id` which doesn't work for lookup and caused `assets.forceCreate` to fail</li>
</ol>

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

[Ref 38](38) attempting the same had failed because:  
  

1.  the asset owner account did not exist
2.  we used \`Raw\` instead of \`Id\` which doesn't work for lookup and caused \`assets.forceCreate\` to fail

- **Problem Statement:** TEER transfer to Asset Hub Kusama requires KSM due to XCM fee payment, with the need for an asset controller.
- **Significance:** Ensuring the correct asset owner account and using the appropriate method for lookup are crucial for successful asset creation.
- **Proposed Solution:** Utilize KSM as an asset on the chain and ensure the asset controller is set up correctly.
- **Expected Outcomes:** Smooth TEER transfer to Asset Hub Kusama with proper asset control and fee payment in KSM.

Register KSM asset on Integritee Network (2nd try)

No Active Proposals