F-2023-0010·code-quality

Consider using named mappings

TL;DR

Solidity 0.8.18 introduced named mappings; using them makes the purpose of each mapping immediately legible without referring to surrounding NatSpec.

Severity
INFO
Impact
LOW
Likelihood
LOW
Method
MManual review
CAT.
Complexity
LOW
Exploitability
LOW
02Section · Description

Description

Consider moving to solidity version 0.8.18 or later, and using named mappings to make it easier to understand the purpose of each mapping.

03Section · Impact

Impact

Code quality and readability only. No security or behavioral impact.

04Section · Recommendation

Recommendation

Adopt Solidity 0.8.18+ and rewrite mappings with named keys and values, for example mapping(address user => uint256 balance) balances;.

F-2023-0010

oog
zealynx

Smart Contract Security Digest

Monthly exploit breakdowns, audit checklists, and DeFi security research — straight to your inbox

© 2026 Zealynx