[Whitelisted Caller] Reduce the number of pending messages allowed in an HRMP channel

Equivalent of Polkadot referenda https://polkadot.subsquare.io/referenda/1740

By default, when opening an HRMP channel, the number of pending messages that can be queued on the relay chain for the channel is the one defined in the active host configuration (HostConfiguration::hrmp_channel_max_capacity).

The current value is 1000 and this referenda proposes to reduce it to 25.

A sending parachain can push at most 1 HRMP message to the relay chain per block while the receiving parachain processes all the pending messages at once. When the limit of pending messages is reached, the sending parachain can't forward any more HRMP message to the relay chain, having to queue them locally. The local queue also has a backpressure mechanism. Even if the receiving parachain has a delay of a couple of blocks in processing the pending messages, 25 pending messages should be enough for everything to work smoothly.

And if we're in a corner case where the receiving parachain is stalled, it's best to not have a lot of pending HRMP messages on the relay chain, since this will increase the load on the receiving parachain when it recovers.

The new limit will apply only to newly opened channels. This will not impact the channels that are already opened, which will keep the old limit.

Also this is just the default limit and it will apply to the channels opened via establish_channel_with_system for example. If a bigger limit is needed for an HRMP channel, there are extrinsics that can be used for setting a custom limit.

Edited

Polkadot wants to change a rule for new communication channels between blockchains.
Currently, up to 1,000 messages can wait in line on the main relay chain.
The proposal is to lower this number to 25 messages for new channels.
This helps keep things running smoothly and prevents big delays.
If a receiving blockchain is stuck, fewer waiting messages means less stress when it starts again.
Old channels will keep the old limit of 1,000 messages.
Special channels can still ask for a higher limit if needed.

Source

Equivalent of Polkadot referenda https://polkadot.subsquare.io/referenda/1740

By default, when opening an HRMP channel, the number of pending messages that can be queued on the relay chain for the channel is the one defined in the active host configuration (HostConfiguration::hrmp_channel_max_capacity).

The current value is 1000 and this referenda proposes to reduce it to 25.

A sending parachain can push at most 1 HRMP message to the relay chain per block while the receiving parachain processes all the pending messages at once. When the limit of pending messages is reached, the sending parachain can't forward any more HRMP message to the relay chain, having to queue them locally. The local queue also has a backpressure mechanism. Even if the receiving parachain has a delay of a couple of blocks in processing the pending messages, 25 pending messages should be enough for everything to work smoothly.

And if we're in a corner case where the receiving parachain is stalled, it's best to not have a lot of pending HRMP messages on the relay chain, since this will increase the load on the receiving parachain when it recovers.

The new limit will apply only to newly opened channels. This will not impact the channels that are already opened, which will keep the old limit.

Also this is just the default limit and it will apply to the channels opened via establish_channel_with_system for example. If a bigger limit is needed for an HRMP channel, there are extrinsics that can be used for setting a custom limit.

Edited