Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

MainToken.__init__() emits Transfer events when the amount minted for msg.sender is zero (and it is always the case) #67

Open
code423n4 opened this issue Nov 6, 2021 · 0 comments
Open

MainToken.__init__() emits Transfer events when the amount minted for msg.sender is zero (and it is always the case) #67

code423n4 opened this issue Nov 6, 2021 · 0 comments
Labels
0 (Non-critical) Code style, clarity, syntax, versioning, off-chain monitoring (events etc), exclude gas optimisation bug Something isn't working sponsor confirmed Sponsor agrees this is a problem and intends to fix it (OK to use w/ "disagree with severity")

Comments

@code423n4
Copy link
Contributor

Handle

pants

Vulnerability details

The function MainToken.__init__() (the constructor) emits Transfer events when the amount minted for msg.sender is zero. This is always the case, as the value of the constant INITIAL_SUPPLY is zero.

Impact

There is no reason to emit these Transfer events because nothing has changed in the system. Such events are only going to confuse users.

Tool Used

Manual code review.

Recommended Mitigation Steps

Emit these events only when the amount minted for msg.sender is not zero.
@code423n4 code423n4 added 1 (Low Risk) Assets are not at risk. State handling, function incorrect as to spec, issues with comments bug Something isn't working labels Nov 6, 2021
code423n4 added a commit that referenced this issue Nov 6, 2021
@code423n4
pants issue #67
ce5a5c9
@code423n4 code423n4 mentioned this issue Nov 7, 2021
Closed
@chickenpie347 chickenpie347 added the sponsor confirmed Sponsor agrees this is a problem and intends to fix it (OK to use w/ "disagree with severity") label Jan 3, 2022
@0xean 0xean added 0 (Non-critical) Code style, clarity, syntax, versioning, off-chain monitoring (events etc), exclude gas optimisation and removed 1 (Low Risk) Assets are not at risk. State handling, function incorrect as to spec, issues with comments labels Jan 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0 (Non-critical) Code style, clarity, syntax, versioning, off-chain monitoring (events etc), exclude gas optimisation bug Something isn't working sponsor confirmed Sponsor agrees this is a problem and intends to fix it (OK to use w/ "disagree with severity")
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@chickenpie347 @0xean @code423n4