You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 makeLaneId
values unique across all bridges).The solutions are:
(ChainId, LaneId)
to identify payment source.It isn't actual now, since we're planning to have only one instance of every pallet initially
The text was updated successfully, but these errors were encountered: