Constructor calls _disableInitializers()
QuickSwap's assessment for RD-F-023 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
V2 core: no proxy, no initialize pattern. V3 Algebra core: direct per-pool deployment — _disableInitializers() is an OZ pattern for proxy implementations, N/A for directly-deployed pool contracts. V3 periphery (SwapRouter, NonfungiblePositionManager proxies): these are proxy contracts but their implementation constructor and _disableInitializers() call status are not documented in any publicly accessible audit.
Sources #
- EtherscanNonfungiblePositionManager Proxy — PolygonscanV3 periphery deployed as proxies — implementation constructors not audited publiclyretrieved 2026-05-16
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 →