Use of _mint in ReraiseETHCrowdfund#_contribute is incompatible with PartyGovernanceNFT#mint
mediumLines of code
Vulnerability details
Impact
Misconfigured receiver could accidentally DOS party
Proof of Concept
if (previousVotingPower == 0) _mint(contributor); <- @audit-issue standard minting here
uint256 tokenId = party.mint(contributor, votingPowerByCard[i], delegate); <- @audit-issue uses party.mint
_safeMint(owner, tokenId); <- @audit-issue PartyGovernanceNFT#mint utilizes _safeMint
The issue at hand is that ReraiseETHCrowdfund#_contribute and PartyGovernanceNFT#mint use inconsistent minting methods. PartyGovernanceNFT uses safeMint whereas ReraiseETHCrowdfund uses the standard mint. This is problematic because this means that a contract that doesn't implement ERC721Receiver can receive a CrowdfundNFT but they can never claim because safeMint will always revert. This can cause a party to be inadvertently DOS'd because CrowdfundNFTs are soul bound and can't be transferred
Tools Used
Manual Review
Recommended Mitigation Steps
Use _safeMint instead of _mint for ReraiseETHCrowdfund#_contribute
