ChainCatcher report: ether.fi has announced the complete removal of its re-staking exposure from weETH, transforming it into a pure liquid staking token (LST), with re-staking functionality moved to a separate token, weETHs, built on Symbiotic. Previously, ether.fi bundled Ethereum staking rewards with EigenLayer re-staking exposure into a single token, making it the largest protocol based on EigenLayer’s re-staking model. Currently, the proportion of re-staked assets on EigenLayer has dropped below 1%, with plans to reduce it to zero by Q3 2026 and fully remove EigenPod withdrawal credentials by Q4. ether.fi CEO Mike Silagadze said: “The end of an era. Sad to see. I still believe re-staking will return in some form—just a bit too early.”
ether.fi Removes weETH Restaking Exposure, Nearly Fully Exits EigenLayer
ChaincatcherShare
Summary
ether.fi announces the complete removal of weETH restaking exposure, repositioning as a pure liquid staking token. The restaking function has been transferred to a new token, weETHs. Previously, the protocol combined staking rewards with EigenLayer restaking in a single token, marking one of the largest token launch events in EigenLayer’s history. Current restaked assets on EigenLayer are under 1%, with a full exit planned by Q3 2026. Mike Silagadze noted that this move closes a chapter but anticipates restaking returning in a different form.
Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.