[TASK] Minimize runtime size and ensure runtime size fits with existing relay chain allowed sizes

[dutterbutter]

Overview

It is recommended to use a compressed version of the runtime to lower the amount of resource consumption as much as possible for the relay chain.

It is recommended to launch a parachain with limited functionality and gradually increase it with runtime upgrades. The reason behind that is that during a runtime upgrade both the previous runtime and the new runtime are included in the PoVBlock and therefore if the changes are large enough the block might be rejected by the Relay Chain due to PoVBlock size limits.

If the runtime is included in the state proof, ensure the PoV block (i.e. the set of extrinsics, including the new runtime, the PoV state proof, potentially the old runtime) fits within the PoVBlock size limit. If the runtime is not included in the state proof, the size limit of the new runtime will be much higher.

We much check the following constraints:

• The runtime version of the relay chain you are targeting (these may change)
• MAX_CODE_SIZE
• MAX_HEAD_DATA_SIZE
• MAX_POV_SIZE

You must have your parachain fit comfortably within these maxima. You can also use the the Polkadot-JS Apps UI connected to a relay node to see these constants:

Developers -> ParachainsConfiguration -> ActiveConfiguration

Tasks

• Determine what pallets to include on launch
• Check if parachain fits comfortably within the maxima mentioned above
• Make any adjustments if necessary