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
At least P/K and Snowbridge shares some commonalities (xcm routing, congestion, dynamic fees, collecting rewards, ...) which are unnecessary implemented twice.
TBD:
one common pallet for relayers and rewards - see comment
store rewards/claims as xcm::Assets
generalize reward/claim identifier to support both P/K and Snowfork bridge
Description
At least P/K and Snowbridge shares some commonalities (xcm routing, congestion, dynamic fees, collecting rewards, ...) which are unnecessary implemented twice.
TBD:
pallet-xcm-bridge-hub-router
for Snowbridge (dynamic fees, congestion)pallet-bridge-messages
on the source/destination chain (without finality pallets) a.k.a. sync finality proofs service #5827pallet-message-queue
for P/K bridge instead custom oneTrait changes:
ExporterFor
changeOption<Asset>
toAssets
orOption<Assets
to support more fees and be aligned withSendXcm
traitExportXcm
- removechannel
and change the order or params:The text was updated successfully, but these errors were encountered: