tbh
98 posts









Hey @LefterisJP, your blame is unfair. There are some facts you did not know. - We located this WETH pool (0x8301) issue at 17:10 UTC on July 30. Unfortunately, we cannot DM @CurveFinance on Twitter because their DM is not allowed. So we shared this finding with a trusted channel and asked him to help forward this finding to the protocol at 17:16 UTC. After that, we actively monitored this pool for any suspicious activities. - Two hours later, at 19:08 UTC, unfortunately, our internal system reported an attack on this pool. This means attackers have also located the same issue and successfully launched the attack. - We need to ensure the protocol and, more importantly, users know this new issue and take action asap to save funds. What’s our choice here? Being an ostrich and putting the head into the sand did not help – attackers have already taken action and will NOT stop. We decided to alert the community and the protocol to take action – the Twitter thread you saw (posted at 19:59 UTC). - Ten minutes later, we got a response from the trusted channel and were notified that "we knew the issue" and tried to rescue but "weren't fast enough". We always stand with the users and help protect the community. Our records of saving and recusing users' funds have spoken for ourselves. We are sorry if you lose your money in the security incident. But your blame on a team trying to help the community is unfair.











