fix: use max assets properly

AstarNetwork · Jan 10, 2024 · 0a6acaa · 0a6acaa
1 parent 60c1e93
commit 0a6acaa
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/runtime/shibuya/src/xcm_config.rs b/runtime/shibuya/src/xcm_config.rs
@@ -52,7 +52,7 @@ use orml_xcm_support::DisabledParachainFee;
 use astar_primitives::xcm::{
     AbsoluteAndRelativeReserveProvider, AccountIdToMultiLocation, DescribeAllTerminal,
     DescribeFamily, FixedRateOfForeignAsset, HashedDescription, ReserveAssetFilter,
-    XcmFungibleFeeHandler,
+    XcmFungibleFeeHandler, MAX_ASSETS,
 };
 
 parameter_types! {
@@ -141,7 +141,7 @@ parameter_types! {
     // For the PoV size, we estimate 4 kB per instruction. This will be changed when we benchmark the instructions.
     pub UnitWeightCost: Weight = Weight::from_parts(1_000_000_000, 4 * 1024);
     pub const MaxInstructions: u32 = 100;
-    pub const MaxAssetsIntoHolding: u32 = 64;
+    pub const MaxAssetsIntoHolding: u32 = MAX_ASSETS;
 }
 
 match_types! {