TransparentBeaconProxy or TransparentUpgradeableBeacon?

Hey guys, just thinking it out, would the same hash collision problem happen in the BeaconProxy pattern as well? Functions in BeaconProxy or UpgradeableBeacon contracts could match with some in implementation contracts. Is there a need for a TransparentUpgradeableBeacon contract?

Note that BeaconProxy doesn't have any external or public functions. So no collisions can happen there. UpgradeableBeacon is not itself a proxy so even if there was a clash with the implementation's functions it would not cause an issue.

1 Like