chore: upgrade to polkadot v1.11.0

[Roznovjak]

TODO:

• pallet_message_queue::IdleMaxServiceWeight config value

NOTES: All changes can be found here:

• https://github.com/paritytech/polkadot-sdk/releases/tag/polkadot-v1.9.0
• https://github.com/paritytech/polkadot-sdk/releases/tag/polkadot-v1.10.0
• https://github.com/paritytech/polkadot-sdk/releases/tag/polkadot-v1.11.0

Breaking changes:

• Remove prometheus RPC metrics substrate_rpc_requests_started and substrate_rpc_requests_finished

Notable changes

• System Callbacks: The system pallet gets five new config items - all of which can be safely set to () as default.

  • SingleBlockMigrations: replaces the Executive now for configuring migrations.
  • MultiBlockMigrator: the pallet-migrations would be set here, if deployed.
  • PreInherents: a hook that runs before any inherent.
  • PostInherents: a hook to run between inherents and poll/MBM logic.
  • PostTransactions: a hook to run after all transactions but before on_idle.

• Add the ability for MessageQueue to process enqueued messages on idle

• Rate limiting for RPC server which can be utilized by the CLI --rpc-rate-limit

• Adds pallet-parameters that allows to have parameters for pallet configs that dynamically change at runtime

• pallet-migrations is introduced that can be configured in the System of a runtime to act as multi-block migrator.

• Add claim_assets extrinsic to pallet-xcm

• The construct_runtime macro now generates a test to assert that all GenesisConfigs of all pallets can be build within the runtime.

• XCM fee payment API: A runtime API was added for estimating the fees required for XCM execution and delivery.

  • fn query_acceptable_payment_assets(xcm_version: Version) -> Result<Vec<VersionedAssetId>, Error>;
  • fn query_xcm_weight(message: VersionedXcm<Call>) -> Result<Weight, Error>;
  • fn query_weight_to_asset_fee(weight: Weight, asset: VersionedAssetId) -> Result<u128, Error>;
  • fn query_delivery_fees(destination: VersionedLocation, message: VersionedXcm<()>) -> Result<VersionedAssets, Error>;

• pallet-xcm's extrinsics teleport_assets and reserve_transfer_assets have been marked as deprecated. Please change their usage to the limited_teleport_assets and limited_reserve_transfer_assets, respectively; or use the generic/flexible transfer_assets extrinsic.

• pallet-xcm's extrinsics execute and send have been marked as deprecated. Please change their usage to the new execute_blob and send_blob. There's a new utility in PolkadotJS Apps for encoding XCMs you can use: https://polkadot.js.org/apps/#/utilities/xcm

• Migrations: prevent accidentally using inner unversioned migration instead of VersionedMigration

• Adds optional HRMP notification handlers to the xcm-executor. These handlers are 3 new config types on the xcm-executor Config trait:

  • HrmpNewChannelOpenRequestHandler
  • HrmpChannelAcceptedHandler
  • HrmpChannelClosingHandler

• The runtime now can provide a number of predefined presets of RuntimeGenesisConfig struct. This presets are intended to be used in different deployments, e.g.: local, staging, etc, and should be included into the corresponding chain-specs.
Having GenesisConfig presets in runtime allows to fully decouple node from runtime types (the problem is described in #1984).

  • The GenesisBuilder API was adjusted to enable this functionality,
  • (Breaking change) Old create_default_config method was removed, build_config was renamed to build_state. As a consequence a node won't be able to interact with genesis config for older runtimes. The cleanup was made for sake of API simplicity.

• New call hrmp.establish_channel_with_system to allow parachains to establish a channel with a system parachain

• (Breaking change) For all authority nodes, the node binary now enforces the presence of a network key, instead of auto-generating when it is absent.

• pallet-xcm has a new extrinsic transfer_assets_using_type_and_then for transferring assets from local chain to destination chain using an explicit XCM transfer types for transferring the assets and the fees:

  • TransferType::LocalReserve: transfer assets to sovereign account of destination
chain and forward a notification XCM to dest to mint and deposit reserve-based
assets to beneficiary.
  • TransferType::DestinationReserve: burn local assets and forward a notification to
dest chain to withdraw the reserve assets from this chain's sovereign account and
deposit them to beneficiary.
  • TransferType::RemoteReserve(reserve): burn local assets, forward XCM to reserve
chain to move reserves from this chain's SA to dest chain's SA, and forward another
XCM to dest to mint and deposit reserve-based assets to beneficiary. Typically
the remote reserve is Asset Hub.
  • TransferType::Teleport: burn local assets and forward XCM to dest chain to
mint/teleport assets and deposit them to beneficiary.
By default, an asset's reserve is its origin chain. But sometimes we may want to explicitly use another chain as reserve (as long as allowed by runtime IsReserve filter).
This is very helpful for transferring assets with multiple configured reserves (such as Asset Hub ForeignAssets), when the transfer strictly depends on the used reserve location. E.g. For transferring a bridged Foreign Assets between local parachains, Asset Hub or the parachain that bridged the asset over must be used as the reserve location. Same when transferring bridged assets back across the bridge, the local bridging parachain must be used as the explicit reserve location. The new method takes a custom_xcm_on_dest parameter allowing the caller to specify what should happen to the transferred assets once they reach the dest chain. The custom_xcm_on_dest parameter should contains the instructions to execute on dest as a final step. Usually as simple as:
 Xcm(vec![DepositAsset { assets: Wild(AllCounted(assets.len())), beneficiary }]),
 but could be something more exotic like sending the assets even further.

• Remove XCM SafeCallFilter for chains using Weights::v3

  • SafeCallFilter was removed from Rococo and Westend relay and system chains as they all now use Weights::v3 which already accounts for call PoV size.
This effectively removes artificial limitations on what users can XCM::Transact on these chains (blockspace limitations are still upheld).