Mappings are best used for dynamic data associations, not statically known associations.
The contract stores constant URIs and Names in mappings, which requires expensive SSTORE operations in the constructor and expensive SLOAD operations in tokenURI().
Likelihood:
Constant, affects every deployment and metadata read.
tokenURI() performs multiple unnecessary state lookups.
Impact:
Very high deployment cost due to writing strings to mapped storage slots.
Increased gas costs when calling tokenURI().
Not applicable - Gas Optimization
Remove both mappings and replace them with dynamic returning inside tokenURI().
The contest is live. Earn rewards by submitting a finding.
Submissions are being reviewed by our AI judge. Results will be available in a few minutes.
View all submissionsThe contest is complete and the rewards are being distributed.