Constructor calls _disableInitializers()
Aerodrome Finance's assessment for RD-F-023 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Pool.sol constructor: constructor() ERC20("", "") ERC20Permit("") {} — no _disableInitializers() call. CLPool.sol: no _disableInitializers() in constructor per source inspection. The master implementation Pool contract is not re-initializable once the factory lock is set on first clone-init call, but the implementation itself has no formal _disableInitializers() guard. Yellow (absent in implementation constructor; no live proxied TVL directly at risk from re-init of master, but hygiene gap).
Sources #
- GitHubPool.sol constructor (raw)Pool.sol raw source — constructor with no _disableInitializersretrieved 2026-05-04
Methodology #
Determine whether implementation contract constructors call `_disableInitializers()` to prevent re-initialization of the implementation directly.
See the full factor methodology and distribution across all protocols →