Blake
1.5K posts





以太坊基金会又出来骚操作了。 为什么大家一直对以太坊基金会印象很差?因为 EF 除了之前攒了一堆圣母和蛀虫围绕 V 神搞小朝廷修仙之外,一直不停的卖卖卖。每年要卖出远超他们正常运营所需的钱,尤其经常在市场不好的时候 dump,。 今天这次进一步引起众怒的原因是,在 AAVE 的 Defi 危机里,整个 DeFi 生态在自救,Lido/Aave/EtherFi 创始人都在捐 ETH的时候,EF 反向操作。 他们非但没有站出来牵头,甚至也没有积极参与,而是在 2387 这个并不算好的价格又套现了 10000 个 $ETH ,而且还有点得意的表示这次我可没有直接砸盘哦,是 OTC 的,快来表扬我。 推文发出引发群嘲。 尤其是在诸多项目响应 AAVE 的"DeFi United"纷纷解囊相助,甚至 @StaniKulechov 都开始开放对散户的募资通道的时候, @ethereumfndn 干出这种事真的非常刺眼。 本来就没啥公信力的组织进一步加深了行业对他们的负面印象,well done,不如早日解散算了吧。



KELPDAO NOTABLY CONTRIBUTES NOTHING TO EXPLOIT RECOVERY AS DEFI RECAPITALIZATION EFFORT REACHES 97% - 43K FREEZE NOT PART OF DEFI SHORTFALL 🚨



I am committing 500 ETH to the Defi united recovery fund. This represents a large part of my crypto holdings, but there are things that are more important than money - Like Stani, I have been working on Aave since the beginning and the only thing I care about is to see it succeed. There are no defeats in life, only lessons. We will be coming back stronger. Aave will win.


Golem Foundation and Golem Factory are contributing a combined 1000 ETH from our treasuries to @aave's coordinated DeFi relief effort following the rsETH incident. We've been working closely with the Aave team this week in a supporting capacity. Our contribution will go toward restoring rsETH backing and enabling an orderly resolution for affected stakeholders. Glad to stand with @aave and the rest of the ecosystem responding here. DeFi United.



Lot's of discussion re: should reETH mainnet holders be affected by kelpDAO LZ bridge hack or not. Some argue that every reETH (on L1 and L2s) is "equal", part of the same "social contract" that should be known to all reETH holders. Also, for all intents and purposes, they are fungible, so how can they not be the same ? Others point out that, from the technical PoV, we actually have two different tokens on mainnet - rsETH and rsETH-OFT wrapper. Is this really a technicality, an unimportant implementation detail, and they are part of the same, common "social contract" or they cannot be ? In my opinion implementation which anyone can (and should) verify should follow a social contract. KelpDAO implemented reETH w/out OFT functionality first. Later, they could have upgraded it to include OFT functionality. The ability to upgrade is part of a social contract (as it can be seen in the code and anyone that buys reETH agrees to the upgradability functionality). Ideally there should be a time delay, so if you are reETH holder and you see an upgrade that you don't like, you can rage-quit. Monitoring of upgrades and time delays should be the norm as is the case in any social contract in the real world - your supplier changes Terms - you should be able to quit the contract But KelpDAO did not do the upgrade. Instead they created a seperate reETH-OFT wrapper. This action cannot be detected by reETH holder just by observing reETH contract onchain. I fail to see how reETH holders could automatically enter the new "social contract" of an OFT version of reETH. The confusion clearly comes from the fact that every single UI, ranging from wallets to exchanges and DeFi apps fooled everybody that reETH and reETH-OFT are the same tokens. No, they are not. They carry very different operational risks. Hiding this fact is something I am strongly opposed to. You want the convenience (and risks) of an OFT token? Fine, issue your token as a pure burn-mint OFT or upgrade the existing token to it. But if you create an OFT wrapper, you create a new token with a new social contract. The main problem with this interpretation is that - ironically - it creates much bigger losses for Aave (see governance.aave.com/t/rseth-incide…), so it is perhaps not surprising that the "all rsETH is the same" theory is being promoted. But don't be fooled - if you are a mainnet rsETH holder, you should not be exposed to rsETH-OFT wrapper risks.


