Normal Behaviour:
Events in Solidity are used to track and log important state changes. In NFT contracts, minting events typically record:
Who received the token (receiver address)
Which token was minted (token ID)
How many tokens were minted in a batch operation (amount)Explain the specific issue or problem in one or more sentences
Specific Issue:
The event parameter is named numberOfSnowman but actually contains the token ID
For a batch mint of 3 tokens starting at ID 5, it will emit
This creates confusion because:
The parameter name suggests it's a quantity
The value is actually a token ID
There's no way to easily track batch mints
Impact:
Indexing Services:
Services like The Graph will index misleading data
Queries for "number of tokens minted" will return incorrect results
Historical tracking of mint batches becomes difficult
Likelihood: Low
Reason 1: The event emission occurs on every single mint operation, making the misleading data consistently present in all minting transactions. Every time a user or contract calls mintSnowman(), the event will emit token IDs under a parameter named numberOfSnowman.
Impact:
Impact 1: Indexing services and analytics platforms will record incorrect minting statistics
The Graph and similar indexers will store token IDs as quantities
Total supply calculations based on event data will be inaccurate
Historical mint batch tracking becomes unreliable
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.