This is a tracking issue to test edge cases with Soroban network configuration changes to fees and limits.
Some examples are,
With network configuration changes in Ledger N+1, validate that ledger N+2 correctly works with new fees and limits in network configuration from Ledger N+1.
With network configuration changes in Ledger N+1, the Tx Set in Ledger N+1 uses the previous configuration values from Ledger N since the new ones are not applied yet.
What?
This is a tracking issue to test edge cases with Soroban network configuration changes to fees and limits.
Some examples are,