The MultiSigWallet contract, designed for dating app users, lacks a critical function to disapprove/revoke transaction approvals. In a dating context, this is particularly severe because:
After a bad date or relationship change, one party may want to revoke their approval
Malicious actors could create and approve harmful transactions, then wait for the other party to blindly approve
Once approved, there's no way to change your mind even if red flags appear
Trust dynamics in dating relationships can change suddenly and dramatically
Users are locked into their approvals even after discovering concerning behavior
Could be used as a form of financial manipulation in toxic relationships
No recourse if one party becomes threatening or untrustworthy after approval
Add a disapproval function and modify the approval tracking:
These changes would make the contract much safer for dating app users by giving them control over their approvals as relationship dynamics change.
Manual Review + Foundry Testing Framework
Please read the CodeHawks documentation to know which submissions are valid. If you disagree, provide a coded PoC and explain the real likelihood and the detailed impact on the mainnet without any supposition (if, it could, etc) to prove your point.
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.