Assessment reportsPublic findings
Back to Zellic site
↗
Assessment reports>Ethereum and Blast Exchanges>Low findings>Lack of storage gap in the contract EIP712VerifierU
GeneralOverview
Findings
High (2)
Medium (1)
Low (3)Calling the function configure regardless of whether the token is rebasingUse of identical domain separatorsLack of storage gap in the contract EIP712VerifierU
Informational (2)
DiscussionLack of documentationCentralization risksEnforce a more recent Solidity version
Threat ModelWhat are threat models?BfxDepositU.solBfxU.solBfxVaultU.solPoolDepositU.solRabbitU.solVaultU.sol
Audit ResultsAssessment Results
Category: Business Logic

Lack of storage gap in the contract EIP712VerifierU

Low Severity
Low Impact
Low Likelihood

Description

When using upgradable contracts, storage gaps are used for reserving storage slots in a base contract, allowing upgrade of that contract to use up those slots without affecting the storage layout. However, the upgradable contract EIP712VerifierU does not have a storage-gap variable, and it is inherited by other contracts.

Impact

If new storage variables are added to the contract EIP712VerifierU in the future, it will affect the storage variables in the child contract.

Recommendations

Consider adding a gap variable to be safe against storage collisions.

Remediation

This issue has been acknowledged by RabbitX, and a fix was implemented in commit a7fa5c60↗.

Zellic © 2025Back to top ↑