F-2025-0007·upgradability-design
Non-upgradeable contract may require complex migration for future changes
TL;DR
Contract is non-upgradeable despite the team planning future modifications, forcing complex user migrations and risk of parallel-contract confusion.
Severity
LOW
Impact
LOW
Likelihood
MEDIUM
Method
MManual review
CAT.
Complexity
LOW
Exploitability
LOW
02Section · Description
Description
The contract is currently implemented as a non-upgradeable contract:
solidity
contract StakingContract is ReentrancyGuard {// No upgrade mechanism}
However, the team has indicated plans for future modifications. Without upgradeability:
- New features will require new contract deployment.
- Users will need to migrate positions manually.
- Complex coordination for rewards and NFT boosts.
- Risk of user confusion during migration.
- Potential for parallel contracts running simultaneously.
03Section · Recommendation
Recommendation
Consider implementing an upgradeability pattern of your choice.
04Section · Resolution
Resolution
Ample Protocol: Fixed. Implemented TransparentUpdatableProxy.
Zealynx: A new issue (F-2025-0010) was found and reported during the upgradeable migration. Update: fixed and verified.
Status
Fixed
