Root + Impact

Description

• Standard ERC-20 implementations (like OpenZeppelin) explicitly inherit from the IERC20 interface (contract ERC20 is IERC20).

  This ensures that the contract actually implements all functions required by the interface and signatures match exactly.

• The ERC20 contract in src/ERC20.sol implements the functions required by the standard (transfer , approve, etc.) but does not mark is IERC20 in its declaration.

Risk

Likelihood:

• The functions are present and public.

  
  

Impact:

• Missing Compile-Time Checks: If a function signature in ERC20 is slightly wrong (e.g., transfer returning void instead of bool), the compiler won't throw an error because it's not trying to match the IERC20 interface.

• Integration Issues: Some smart contract tools or EIP-165 checks (if added later) might rely on explicit inheritance to verify compliance.

Proof of Concept

Recommended Mitigation