Repository navigation
Investigate and replace xc-asset-config pallet with orml asset-registry #1468
Description
Explore if asset-registry pallet from orml can replace our xc-asset-config pallet. The orml pallet is preferred due to it's wider usage across ecosystem and will reduce our maintenance burden
What to do?
- Investigate
asset-registrypallet, how it's used in other parachain and it's viability for replacing xc-asset-config pallet - Replace xc-asset-config with it (need storage migration to remove pallet and keys) if effort makes sense
(in case too much work is needed, we can omit it)
Activity
ashutoshvarma commentedon Jul 16, 2025
Not required, current pallet works just fine but just awkward to use as designed to only contains latest xcm storage types (V5 rn).
It is breaking change and will require coordination
Dinonard commentedon Jul 16, 2025
I see, makes sense.
Given we get very little, or nothing by this, I hope we can avoid this change then.
I don't remember the exact reason why I did it like that, but there was some problem back then with storing
VersionedLocationinto storage. We can revisit that if it helps.However, can this migration be avoided?
Eventually old XCM versions will be deprecated, impacting the
Versionedenum as well.ipapandinas commentedon Sep 8, 2026
ORML deps will be removed in the upcoming
runtime-2500