GPT-5 finding
updateBeneficiary allows transferring shares to the zero address, making future fee claims impossible (funds stranded)
highapi-contracthigh
- src/base/FeesManager.sol
There is no validation preventing newBeneficiary from being address(0). If set to zero, only the zero address can claim fees, which is impossible. Shares become unclaimable and accumulate permanently, effectively stranding funds associated with those shares.
Recommendation
Add a require(newBeneficiary != address(0)) check (using a custom error if desired) and consider preventing transfer to contracts lacking fee-collection capability if that’s a concern.