The error message for token decimals validation is misleading and does not match the actual validation logic.
The contract throws an error suggesting validation for decimals > 18, but actually throws when decimals = 0:
Misleading error messages
Confusion for integrators and users
Manual code review
Correct error message to match validation logic
Add separate validation for zero decimals
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.