Compound Developer Community Call – October 6, 9:30am PT

On October 6, at 9:30am PT, the Compound community will hold its next Developer Community Call. This will be an open discussion forum for individuals and organizations developing protocol improvement proposals or building applications and projects that integrate the protocol.

Below is the high-level agenda for the upcoming call. Note that this call belongs to the community, and as a community member you are empowered to take this call in any direction you think best benefits the community. If you wish, you may help organize it, structure its agenda, lead it, etc.

  1. Welcome: Adam will recap the ground rules for the call.
  2. Proposal/Project Discussions : The following community members have volunteered to discuss specifics around the COMP Distribution bug introduced in Proposal 62.
  • Tyler Loewen - COMP Distribution Bug Overview
  • Robert Leshner - Community Response and Updates
  • Open Discussion on Next Steps and Code Review Practices

If there are any other proposals, projects, or topics you’d like to add to the agenda, please post on this thread or in the Compound Discord. Everyone is welcome to participate and contribute.

Lastly, the call will be audio-recorded; the recording and written notes will be shared in this thread for anyone who can’t make it.

Hope to see you on the call tomorrow!

For those of us that need a little more context, I would suggest adding an item for discussing the broader decentralization push by Compound. From my perspective, it looks like there is a very small group of contributors on the forum and a largely abandoned discord and unclear who is taking responsibility/accountability for issues like this, or even the messaging to the many affected parties.

Many of us want to see compound remain as the yield backbone of defi, but my takeaway from this episode is “no one is behind the wheel”. I may be wrong on that but its hard to square that with what I can follow compound labs is doing with institutional investors, gateway, treasury. It could be I am misreading the situation, but it looks to me like the core of compound has been abandoned to the community, letting issues like this appear with no clear accountability (i.e. the community did it and the community will fix it) while the core team has moved on to other projects. I genuinely want to see the protocol succeed but this has brought to light a lot of shortcomings of decentralization. Addressing this bug is obviously super important but systemically there seems to be a problem with how compound has organized (or de-organized) its core operations.


Recording of the call from Adam B. CDCC-2021-10-06.mp3 - Google Drive