[Forum Post](https://forum.moonbeam.network/t/proposal-48-register-movr-in-kusama-assethub/1440)

**Abstract** -  This proposal is to register MOVR as a foreign asset in Kusama AssetHub. It is the first step to be able to teleport MOVR in/out of Kusama AssetHub, as some XCM filters for teleportation need to be added in the Moonriver runtime.

**Details** - AssetHub added the possibility of registering foreign assets via the `ForeignAssets` pallet.

The main purpose of this proposal is to register MOVR as a Foreign Asset in Kusama AssetHub. Kusama AssetHub might play a pivotal role as a infrastructure chain in Kusama for assets, similar to Noble for the Cosmos Ecosystem. Consequently, users or service providers should be able to move MOVR in/out of Kusama AssetHub as they please. One use case can be to provide MOVR liquidity to the future Kusama AssetHub DEX.

This proposal would have to go through ROOT track because it sends an XCM message as the Moonriver Sovereign account.

The proposal was tested via Chopsticks with Moonriverruntime 2602 and Kusama AssetHub runtime 1000000.

[Encoded Call Data to Register MOVR in Kusama AssetHub](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-asset-hub-rpc.polkadot.io#/extrinsics/decode/0x35000102009d1f040a007369626ce707000000000000000000000000000000000000000000000000000001000000000000000000000000000000)
[Encoded Call Data to Set MOVRMetadata in AssetHub](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-asset-hub-rpc.polkadot.io#/extrinsics/decode/0x35110102009d1f040a284d4f565220546f6b656e104d4f565212)
[Encoded Call Data to Batch Both Actions into Two Separate XCM Messages](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fwss.api.moonriver.moonbeam.network#/extrinsics/decode/0x1e0208670003010100a10f0310000400010000070010a5d4e81300010000070010a5d4e8001608140d010204000101007369626ce70700000000000000000000000000000000000000000000000000000603070050d6dc0102d00700e835000102009d1f040a007369626ce707000000000000000000000000000000000000000000000000000001000000000000000000000000000000670003010100a10f0310000400010000070010a5d4e81300010000070010a5d4e8001608140d010204000101007369626ce70700000000000000000000000000000000000000000000000000000601070050d6dc0102d007006835110102009d1f040a284d4f565220546f6b656e104d4f565212)

Screenshots of end result simulated via Chopsticks:
**![|1355x788](upload://qyqE24N9euklHTDzcFtC3PqsOlP.png)**
**![|1170x965](upload://jCvO9vrrEQDGsggEwv7wFlM42j2.png)**

**The main requirement is that Moonriver Sovereign Account on Kusama AssetHub must hold at least 1 Transferable KSM.**

- **Problem Statement:** Statemint collators faced block production issues due to a key type mismatch between sr25519 and ed25519 keys.
- **Significance:** Ensuring block production continuity and validator validation on the Relay Chain.
- **Proposed Solution:** Implement a temporary runtime fix enabling ed25519 in Aura for Statemint, followed by a subsequent upgrade to revert Aura to using sr25519 keys.
- **Expected Outcomes:** Restoration of block production functionality and successful validation of collator signatures on the Relay Chain.

#48 Register MOVR in Kusama AssetHub