Compound Contributor Grants

Given some comments we’ve received, we wanted to clear up a few things regarding the initial grant payment. Firstly, the 1000 COMP payment covers the development expenses and the audit for the entire set of changes:

  • grantComp (PR #79)
  • Vesting (PR #71)
  • Distribution improvements

We plan to see the remaining proposals through and do not plan to request any additional grant.

Also @arr00 - as far as communication processes go, I think this 1 week policy is a great rule of thumb for future proposals. The changes have been discussed on the recent developer calls and the code has been available for review on Github for a few weeks now, but posting on the forums more frequently in the future is an obvious improvement to community involvement. We had a strong bias towards pushing this one out because we wanted to enable the community to decide how to compensate users affected by the recent DAI liquidation incident.

Hopefully, the existence of the grant function will help spearhead the discussion about how grants should function and the procedure around them. From our perspective, we wanted to set the following precedents:

  1. People who take on larger development projects, like those requiring audits, can be compensated for those changes
  2. Not all work needs to be done speculatively. Currently, anyone contributing needs to make changes on the off-chance those are later accepted by the protocol. In this case, we’ve completed all of this work ahead of time. However, hopefully by requesting payment before all of the changes are deployed, we can take a small step in direction that is more appealing to contributors.

Also - great catch by @jvaqa! We’ll send a bug bounty for identifying the issue in _setContributorCompSpeed.

5 Likes