[Proposal: 41] Register GLMR in AssetHub (Re-do)

Vote on Proposal 41

Abstract - Proposal 37 to register GLMR in AssetHub failed due to the lack of support. This is a redo of that proposal. Therefore, it will register GLMR as a foreign asset in Polkadot AssetHub.

For GLMR to be moveable to AssetHub, some other things must happen, so this is only the first step to achieving that.

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

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

This proposal has to go through ROOT track because it sends an XCM message as the Moonbeam Sovereign account.

The preimage from Proposal 37 will be reused, which is 0x91c1540b78c2dda3fc0773b5b944d8a8536c5158bf5616395b133c4eb054799f.

Once again, the proposal was tested via Chopsticks with Moonbeam runtime 2700 and Polkadot AssetHub runtime 1000000.

It sends two separate XCM messages, one to register the asset and the other to set the asset Metadata.

Encoded Call Data to Register GLMR in Polkadot AssetHub

Encoded Call Data to Set GLMR Metadata in Polkadot AssetHub

Encoded Call Data to Batch Both Actions into Two Separate XCM Messages

Screenshots of end result simulated via Chopsticks.



The main requirement is that Moonbeam Sovereign Account on Polkadot AssetHub must hold at least 12 Transferable DOTs.


I am in support once again!


Let’s make sure it passes this time :+1: