F-2024-0006·naming-convention

Use camelCase for immutable variables

Acknowledgedvaultyieldbtc
TL;DR

The contract uses uppercase for the immutable variable FEE_RECIPIENT. Renaming to camelCase feeRecipient distinguishes it from constants and aligns with Solidity naming conventions.

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

Description

The contract uses uppercase for the immutable variable FEE_RECIPIENT. While this is commonly used for constants, it's generally recommended to use camelCase for immutable variables to distinguish them from constants.

03Section · Recommendation

Recommendation

Rename FEE_RECIPIENT to feeRecipient for consistency with Solidity naming conventions.

F-2024-0006

oog
zealynx

Smart Contract Security Digest

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

© 2026 Zealynx