The InheritanceManager
contract lacks a receive()
function, preventing it from accepting native Ether deposits. Consequently, the sendETH()
functionality becomes unusable as the contract cannot hold Ether. This limits the contract's utility to managing only ERC20 tokens.
The absence of a receive()
function in the InheritanceManager
contract means that any attempt to send Ether directly to the contract address will revert. This is demonstrated by the following Foundry test:
The contract's inability to receive Ether renders the sendETH()
function ineffective. This significantly restricts the contract's functionality, limiting its ability to manage and distribute Ether as part of the inheritance process. Users can only utilize the contract for managing ERC20 tokens, which reduces its overall utility and deviates from its potential scope.
Manual review and foundry test
Implement a receive()
function within the InheritanceManager
contract to enable it to receive Ether.
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.