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.

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

Support pallet instances in bridge-relayers pallet #1692

Closed
svyatonik opened this issue Dec 2, 2022 · 1 comment
Closed

Support pallet instances in bridge-relayers pallet #1692

svyatonik opened this issue Dec 2, 2022 · 1 comment
Assignees

Comments

@svyatonik
Copy link
Contributor

After #1654 we are identifying "bridge" in bridge-relayers pallet with LaneId. But it isn't consistent with out other pallets. The current approach is 1 grandpa + messages pallet for single bridged chain (parachains is a bit different - it supports all parachains of the bridged relay chain). And since we don't support instances in the relayers pallet, it would mean that it may only be used by single bridge (unless we make LaneId values unique across all bridges).

The solutions are:

  • add instances support to the bridge-relayers pallet;
  • use pair (ChainId, LaneId) to identify payment source.
    It isn't actual now, since we're planning to have only one instance of every pallet initially
@serban300
Copy link
Collaborator

Resolved by #1907

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants