Proposal 65: Correct Over-Accrued COMP

Thanks for the feedback, a16z and Gauntlet.

These changes were put together and proposed much quicker than most other proposals. While Compound is no longer at risk of losing additional COMP, the protocol is still not fully functional - users active in the affected markets are not able to withdraw their accrued COMP. If the protocol were fully functional, these changes certainly would have had a lot more public discussion before being submitted for a vote.

Getting Compound protocol to a fully functioning state with minimal downtime is my #1 priority. This partial downtime of COMP rewards can have negative effects on both users, other protocols, and developers. What if a user’s/protocol’s business logic relies on receiving the accrued COMP tokens and they’re unable to claim them?

We all know Compound’s governance is disorganized, and there are only a few busy individuals who are capable of seeing changes through all the way to proposal execution. It’d be terrible for this partial downtime to drag on for months due to this.

1 Like