Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support V2 XcmExecutor #36

Closed
gregdhill opened this issue Sep 5, 2022 · 2 comments
Closed

Support V2 XcmExecutor #36

gregdhill opened this issue Sep 5, 2022 · 2 comments

Comments

@gregdhill
Copy link
Contributor

The trait bound here should use xcm::v2::ExecuteXcm for the latest XcmExecutor.
@jerrybaoo
Copy link
Collaborator

jerrybaoo commented Sep 6, 2022 •
edited

Because ZenlinkProtocol Pallet is currently not suitable for cross-chain asset transfer, it may lead to asset fragmentation on parachain. We plan to do cross-chain transactions based on the cross-chain asset transfer function of the chain itself. Therefore, it is better to turn off the cross-chain asset transfer function for now and set XcmExecutor to () in the Runtime configuration. Maybe we should have ZenlinkProtocol as a pallet focused on AMM. XCM cross-chain transactions as a separate pallet.

@jerrybaoo
Copy link
Collaborator

https://github.com/zenlinkpro/bifrost/blob/develop/runtime/bifrost-kusama/src/lib.rs#L1857．This is a configuration in a production environment. It runs stably on bifrost kusama.

@gregdhill gregdhill mentioned this issue Sep 7, 2022
Closed
@gregdhill gregdhill mentioned this issue Oct 28, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gregdhill @jerrybaoo