Unresolved concerns

• The appropriate minimum value threshold ($1,000) for qualifying accidental transfers needs further discussion.— massnomis
• Whether other cToken implementations (COMP, USDT, DAI) should also be upgraded now rather than waiting until funds are actually trapped in them.— rleshner, arr00
• Clarity on how retroactive claims (accidents older than 6 months) would be handled and what the exact request process looks like.— cryptotyrel
• Many token types (e.g., immutable cTokens, underlying-token deposits, phishing losses, slippage losses) are fundamentally unrecoverable under this mechanism, leaving affected users without recourse.— blck, arr00, boblogiii

Notable participants

• arr00Proposer who designed the policy, wrote the sweepToken code, ran simulations, and has continued to administer fund-return requests for years after the original proposal.
• rleshnerCore contributor who reviewed technical details, endorsed the COMP reward rationale, and later clarified governance policy on unrelated Uniswap airdrop claims.
• massnomisEarly supporter who raised concerns about reward sourcing and precedent-setting implications of the policy.
• johndohRaised the question of whether the sender should bear a penalty for causing the accidental transfer.
• blckVerified the deployed contract bytecode and explained technical limitations on which tokens can and cannot be recovered.
• cryptotyrelAsked about retroactive application of the policy and the request process, ultimately expressing support.
• gettySuggested extending the sweep functionality to other cToken contracts and preventing further accidental transfers to cUNI.
• LaviAsked where the 10% penalty funds would go, prompting clarification that they return to the Timelock/protocol.