You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is possible for vaultFee to be non-zero but the receiver of the fees, feeCollector, to remain the default address(0) value.
Technical Details
The GVault default is to have vaultFee and feeCollector remain unset, which keeps them at the default values of 0 and address(0) respectively. It is possible for vaultFee to be set to a non-zero value while feeCollector remains at zero, resulting in fees getting sent to address(0).
Impact
Informational.
Recommendation
Protections for owner errors are not strictly needed, but if guardrails against contract owner errors are worth some gas, consider this change:
It is possible for
vaultFee
to be non-zero but the receiver of the fees,feeCollector
, to remain the defaultaddress(0)
value.Technical Details
The GVault default is to have
vaultFee
andfeeCollector
remain unset, which keeps them at the default values of0
andaddress(0)
respectively. It is possible forvaultFee
to be set to a non-zero value whilefeeCollector
remains at zero, resulting in fees getting sent toaddress(0)
.Impact
Informational.
Recommendation
Protections for owner errors are not strictly needed, but if guardrails against contract owner errors are worth some gas, consider this change:
The text was updated successfully, but these errors were encountered: