Support XCM

[sirius651]

Pull Request Summary

Describe what changes this pull request makes to the repository

Check list

• contains breaking changes
• adds new feature
• modifies existing feature (bug fix or improvements)
• relies on other tasks
• documentation changes

This pull request makes the following changes:

[sirius651]

@impelcrypto Updated useXcmBridge hook but still not finished yet :(. will let you know once it done.

[github-actions]

Visit the preview URL for this PR (updated for commit 661b650):

https://astar-apps--pr394-feature-xcm-asset-qskhh23h.web.app

_{(expires Wed, 25 May 2022 14:16:34 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

[sirius651]

Hi @impelcrypto , I updated RelayWidget and hooks for binding the data on that. I'll keep updating hooks & testing stuff, but you can go ahead implementation of bridge from now on.

[hoonsubin]

I don't think this is a scalable solution. Why don't we create an interface that handles the chain data like name and icon (and maybe the asset info too), and move that to a config file?

For example,

interface XcmNetwork {
   name: 'Polkadot';
   icon: './path/to/dot.png';
   endpoint: 'wss://...';
   asset: XcmAsset;
}

and create an object with the type:

interface XcmChannel {
   astar: XcmNetwork[];
   shiden: XcmNetwork[];
   shibuya: XcmNetwork[];
}

This is just an example, but because we plan to add more channels and we want this process to be scalable, code structure is key I think

[hoonsubin]

LGTM

[Kahonnohak]

LGTM!