This issue pertains to a contract upgrade in which the new contract, ThunderLoanUpgraded.sol
, has a different variable order, leading to disruption in the original storage structure.
In a foundry test, it was observed that when upgrading the contract ThunderLoan.sol to the new contract ThunderLoanUpgraded.sol
, the order of variables in storage differs. This discrepancy results in the disruption of the original contract's storage layout.
The impact of this issue is assessed as medium. During the period when the contract is in an upgraded state, the protocol may operate incorrectly. However, it is important to note that this issue can be resolved by performing another upgrade.
Foundry
To address this issue, it is recommended to rectify the contract ThunderLoanUpgraded.sol
before executing any further upgrades. Ensuring consistency in the storage structure between the original and upgraded contracts will prevent the disruption of storage during future upgrades, maintaining the integrity and stability of the protocol.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.