Retroactive reimburesement for para upgrade fees contributions

When a parachain is registered, the parachain manager is responsible for the cost of storing the validation code on-chain. After successful registration in the current system, parachains are allowed to perform code upgrades without being required to pay for the differences in validation code size.

This means that someone could theoretically register a parachain with minimal code and then, at a later point, freely register validation code that is significantly larger than the original code.

This is obviously a problem that needs to be fixed, as being imprecise about the deposit requirements for storing data on-chain can lead to issues in the system.

This is something that needs to be fixed before the release of the new Coretime model.

In PR #2372 I have proposed a solution that would solve this problem and I implemented it. However, after having a lot of meaningful discussions on this PR a different approach was proposed where the dynamic fee based model that was implemented in this PR would be added at a later stage.

PR #3020 Is the implementation of phase #1 described in the proposed approach.

This is something I have dedicated a lot of my time to and I would love to continue working on this.

This is a tip request for the efforts I've invested so far.

A parachain is a type of blockchain that needs to register to work.
When a parachain is registered, the manager must pay to store its code.
After registration, parachains can upgrade their code without extra costs.
This can cause problems if a parachain starts with small code and later uses a lot more.
It's important to fix this issue before the new Coretime model is launched.
A solution was proposed and worked on to make things better, but a new idea was suggested instead.
The new idea will be worked on in phases, starting with an initial phase.
The author wants to continue helping with this project and is asking for support for their efforts.

Source

When a parachain is registered, the parachain manager is responsible for the cost of storing the validation code on-chain. After successful registration in the current system, parachains are allowed to perform code upgrades without being required to pay for the differences in validation code size.

This means that someone could theoretically register a parachain with minimal code and then, at a later point, freely register validation code that is significantly larger than the original code.

This is obviously a problem that needs to be fixed, as being imprecise about the deposit requirements for storing data on-chain can lead to issues in the system.

This is something that needs to be fixed before the release of the new Coretime model.

In PR #2372 I have proposed a solution that would solve this problem and I implemented it. However, after having a lot of meaningful discussions on this PR a different approach was proposed where the dynamic fee based model that was implemented in this PR would be added at a later stage.

PR #3020 Is the implementation of phase #1 described in the proposed approach.

This is something I have dedicated a lot of my time to and I would love to continue working on this.

This is a tip request for the efforts I've invested so far.