The current way of constructing the Budget from config enforces the config size must match the protocol-defined count (ContractCostType::variants().len()). While this ensures the validity of the config entry for the current protocol, it does not take into consideration config from an earlier protocol, with fewer number of cost types.
What
Resolves #1388
Why
The current way of constructing the Budget from config enforces the config size must match the protocol-defined count (
ContractCostType::variants().len()). While this ensures the validity of the config entry for the current protocol, it does not take into consideration config from an earlier protocol, with fewer number of cost types.Known limitations
[TODO or N/A]