The codebase contains two different constants for the upgrade name:
If any part of the protocol relies on UpgradeName for version checks or upgrade logic, it will use an incorrect version (0.0.0)
The duplicate constants violate the DRY (Dont Repeat Yourself) principle and make maintenance error-prone. There could easily be an error because of this.
Consider consolidating the upgrade name constants into a single location and use a single source of truth.
