Unused custom errors increase code noise and indicate inconsistent revert pattern usage

Description

• The contract defines multiple custom errors that are not referenced anywhere in the codebase. Instead, the contract relies on inline require statements with string-based revert messages.

• The presence of unused errors increases code noise and may indicate incomplete refactoring or inconsistent design choices in revert handling.

Risk

Likelihood:

• The unused custom errors are present in the deployed contract as defined but unreferenced declarations, making this a certainty rather than a conditional occurrence.

• Any future developer or auditor reading the codebase will encounter this inconsistency, as the contract simultaneously defines custom errors and uses string-based require statements throughout.

Impact:

• The presence of unused errors increases code noise and may indicate incomplete refactoring or inconsistent design choices in revert handling.

Proof of Concept

Recommended Mitigation

Either remove unused custom errors to reduce code clutter, or refactor the contract to consistently use custom errors instead of string-based require statements.