- Compound CEO is humbled by the COMP community.
- Robert Leshner took to Twitter to demand the return of large accidental COMP rewards.
- The COMP community disagrees with his approach.
The CEO of Compound (COMP) learns a lesson in humility from his beloved COMP community. The CEO — Robert Leshner, took to Twitter to express his feelings over the recent error in the Compound liquidity mining reward program.
In detail, he addresses those users who received a large amount of COMP from the protocol error a couple of days ago. To specify, he requests them to return these large rewards to the Compound Timelock.
Although, as a bonus, he said that those who do return the funds can keep 10% of the funds as a white-hat. However, he adds that those who fail to do so will be reported to the IRS and will also be doxxed.
This led to a myriad of responses from the Twitter sphere. Some say that they’d rather pay the IRS tax than return the funds. Others laughed saying that they are not based in the USA. Meanwhile, one reply stood out the most.
To highlight, this response calls out hypocrisy. It says that when users accidentally send tokens to the wrong address then there is no chance for a refund. So why should there be such dramatic legal action when the same happens to a big project?
Humbled by this, Leshner responds to the community with a new much mellow tweet.
I’m trying to do anything I can to help the community get some of its COMP back, and this was a bone-headed tweet / approach. That’s on me.
Luckily, the community is much bigger, and smarter, than just me.
I appreciate your ridicule and support.
— Robert Leshner (@rleshner) October 1, 2021
He says that his intention was to simply help the community retrieve some of the lost COMP it lost. He also apologizes for his initial ‘bone-headed’ response.
Above all, he expresses his gratitude for the community. In particular, he says the community is bigger and smarter than he is and is grateful for their honesty and support. As for resolving the error, SushiSwap coder — Mudit Gupta, tracked it down.
To emphasize, the issue came from a one-character error on the protocol. Specifically, an ‘>’ instead of an ‘>=’ was to blame. All in all, the community has now proposed a change to fix this error. The proposal will likely pass on October 7, 2021.
- Bistroo Network Solves Restaurant-Food Delivery Problems
- Breaking: White House Darknet Market Reveals Retirement Plans
- VeChain’s NFT Project: VIMworld Launches Its Own Discord Server
- The Crypto Market Goes Parabolic, OMG May Hit The Moon Soon?
- Investors Now Moving To Solana and Cardano As Ethereum Loses Steam