While the DeFi world was busy chasing #ETH restaking yields, a hidden bug in Kelp DAO’s fee contract turned the protocol against itself. The result: excess rsETH minting and an emergency pause on all operations.

The Kelp DAO team announced on X that they discovered a critical bug in their fee contract. The bug was causing the system to mint more rsETH liquid restaking tokens than it should have. In simple terms: the code was printing extra rsETH, threatening the token’s balance and peg. #rsETH

Why Did the Protocol Hit Pause?

This wasn’t an external hack draining wallets. It was an “attack” from inside the code. As soon as the team detected the issue, they paused deposits and withdrawals. The reason was clear: if incorrect minting continued, rsETH could depeg and users’ restaked positions could face losses.

Where Was the Actual Problem?

The bug lived in the fee contract — the same contract responsible for calculating and distributing fees. It inadvertently triggered over-minting of rsETH. The team is still detailing the specifics while working on a fix.

DeFi Lesson: Code Is Law, and Bugs Are Expensive

#KelpDAO ’s move was proactive. Pausing is disruptive for users, but necessary to protect protocol integrity and asset security. This wasn’t a hacker stealing funds; it was an internal bug that made the system its own enemy.

What’s Next?

The team is fixing the bug. Operations will resume after audits confirm safety. rsETH holders have to wait for now. Kelp DAO had previously announced Chainlink oracles and CCIP integration to strengthen KUSD, but fixing the house comes first.

Bottom Line: In DeFi, “trustless” means “code is law.” And when the law has a bug, the biggest attack comes from within. Kelp hit pause to stop the bleeding. Now the real test is how fast and transparent the recovery will be.