Skip to content

Conversation

godzillaba
Copy link
Contributor

the empty constructor in aeERC20 can cause issues with explorer verification because the built constructor code differs from the code used by CreationCodeHelper

@cla-bot cla-bot bot added the cla-signed label Dec 18, 2024
contract aeERC20 is ERC20PermitUpgradeable, TransferAndCallToken {
using AddressUpgradeable for address;

constructor() initializer {
Copy link
Member

@gzeoneth gzeoneth Dec 18, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if this is removed, the logic contract would become initializable
while I don't think it will causes any problem in our usecase especially when self-destruct no longer delete code, it is something we should think about; in L2AtomicTokenBridgeFactory we call initialize on the logic contract (which should not be callable if it were deployed normally because of the constructor) deployed by CreationCodeHelper trick to prevent those logic from being re-inited

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants