This caused adverse reaction from the community. Andre Cronje, the founder of popular DeFi covenant yEarn.Finance highlighted the disparity through a tweet:
The next voting related to the protocol is scheduled for August 28. Egorov, at the time of writing this article, has a voting power of over 50%.
A week before, when YFValue was rolled out, it had an ingrained vulnerability that would have permitted its developers to permanently freeze users’ staked tokens. This reminded about Yam.Finance, which was rolled out with a comparable problem, even though YFValue’s vulnerability does not seem to be that severe.
As YFValue began to rollout next day, it tabled a self-centered mining chance for a handful of “clever” members of the group:
We are having the first community discussion: governance proposal CIP-1 (# cip-1-feedback on Discord)!
TLDR: do we want a pool which receives $COMP, do we want a withdrawal fee there to be introduced and to burn $CRV, and whether $COMP rewards should be boosted by $CRV. pic.twitter.com/su9fs6tY71— Curve (@CurveFinance) August 23, 2020
Nevertheless, intelligent members of the group identified the issue and benefited by carrying on with farming in pool 0 in spite of caution and deletion of the frontend UI. As there was no other way to halt the process, the core team went ahead and burned the minter key. “This key burn would cause tx failure at checkNextEpoch (08/24/2020 @ 7:52am (UTC), an event which we hoped would serve as a deterrent.”
With the aforesaid burning of minter key, those who continue to retain their funds from the specific pool before the time limit could lose their tokens once and for all.