A few short-term personal thoughts.
I don’t speak for the EF, so want to share a subjective view (which can be bent - I have no ego in this, so please fire away) ⤵️
1. I was silent because there is nothing of hard substance to communicate. Firstly, communicating about abstaining does no good and only makes the efforts of protocols working on a resolution - harder. It might also throw implicit shade (which there is none). So why do that. Secondly, communicating “we are speaking to the parties involved and hope a resolution is found soon” is wordsalad. I don’t appreciate such empty statements by third parties. When affected protocols do it, it makes sense, because they need to do it for legal and optics reasons. But EF doesn’t make decisions for protocols, doesn’t control any of those keys or permissions, none of that - so it can’t speak for others. While we did talk and gave our opinions, such situations are ultimately up to the teams’ legal counsel, ethics, abilities, vision, funding. Those that pull through are the heroes here - and not us who “oh ye we talked to teams”. I find such comms to be rude instead if released.
2. On the inaction so far, many founders have already expressed why they think that: creating a dangerous precedent. But that reasoning reads rude at first. You immediately get hit with “but it is one of the main OG protocols, it is contagion, etc.” Arguing on the severity is moot, but I also never pulled out my personal lending balance from Aave (I have on Morpho, Spark, Gearbox, Liquity, and more too) so that says something? It’s tough but it’s a resilience test. If you plug this hole even a bit, it’s not just about the future, it’s also about past teams being rightfully very mad for not getting such support before. And then what about permissionless protocols, curated instances? Gets even messier. What EF did do is - reduce the debt of
@LidoFinance /
@mellowprotocol vaults and relieve their pain from high borrow rates (by swapping the position:
nitter.net/ethereumfndn/status/20…). EF gets liquidity, treasury is safu at 1:1, Lido/Mellow cover their debt and save a lot. Is this an ecosystem-wide help? Personally I treat it as a neutral move, it’s maybe tiny positive in fact, but not worthy of self-glazing.
I personally find it amazing that the community came together and has now almost fully closed the hole. Well done to the parties involved, and on the great branding around it (cc
@aave). The least we could have done, if not being active, is to stfu and let them cook. We don’t need to give opinions and say “oh, why this way, and not another way to deal with it”. Time constraints, stress, multiple parties involved, etc. - this is why it’s up to the teams to man up, these are their businesses and decisions. We must trust them to be grown-up, mature, and ready to survive situations like this. It’s okay to disagree here, I disagree with myself here (I hate both sides in this case).
3. We obviously want to talk about security, standards, efforts to avoid such cases, etc. - but now is bad timing. Putting salt on the wound is not a good idea, so we will address this in due time (so will the teams, without EF hand-holding anyone).
4. Also on tone deaf, sure the EF still appears like that sometimes, for example, the timing of the last periodic sale was crap, no way around it. All the troll memes are deserved, but they don’t change all the other good initiatives EF is working on. Not everything can be perfectly timed when there are many parallel things involved. On that specific sale I already posted here
nitter.net/ivangbi_/status/204193… and here
nitter.net/ivangbi_/status/204772….
——
I hope to appear logical and open-agile in anything I touch with regard to EF + DeFi, even if I am often not responsible for that and have no direct say in it. I hope this reply and others show the logic more clearly and allow for a discussion if needed. I don’t do this for the money honestly, and thus I am also not a fan of self-glazing empty statements.