In the protocol, several immutable
and constant
variables are declared without the private
visibility specifier. Marking these variables as private
can save deployment gas.
Immutable and constant variables declared with default or public visibility result in the compiler generating non-payable getter functions. This increases the deployment gas cost and adds unnecessary entries to the method ID table. By marking these variables as private, the contract can avoid these additional costs while still allowing the values to be read from the verified contract source code.
By not marking immutable and constant variables as private, the contract incurs higher deployment gas costs. This can be particularly impactful for contracts deployed frequently or on a large scale.
Manual review.
Update the visibility of immutable and constant variables from public
to private
.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.