Market Cap: $3.2904T 0.530%
Volume(24h): $108.896B -5.760%
  • Market Cap: $3.2904T 0.530%
  • Volume(24h): $108.896B -5.760%
  • Fear & Greed Index:
  • Market Cap: $3.2904T 0.530%
Cryptos
Topics
Cryptospedia
News
CryptosTopics
Videos
Top News
Cryptos
Topics
Cryptospedia
News
CryptosTopics
Videos
bitcoin
bitcoin

$107974.534475 USD

1.34%

ethereum
ethereum

$2493.945606 USD

1.64%

tether
tether

$1.000258 USD

-0.03%

xrp
xrp

$2.198357 USD

0.63%

bnb
bnb

$649.022733 USD

0.63%

solana
solana

$145.932687 USD

-0.07%

usd-coin
usd-coin

$0.999502 USD

-0.05%

tron
tron

$0.273746 USD

0.23%

dogecoin
dogecoin

$0.166063 USD

-0.12%

cardano
cardano

$0.575474 USD

-1.89%

hyperliquid
hyperliquid

$37.553539 USD

-2.76%

bitcoin-cash
bitcoin-cash

$484.102244 USD

2.24%

sui
sui

$2.771720 USD

-1.31%

chainlink
chainlink

$13.366183 USD

-0.20%

unus-sed-leo
unus-sed-leo

$9.003490 USD

-0.36%

Cryptocurrency News Articles

zkLend's Shutdown: A Starknet Protocol Falls Victim to Exploit and Market Forces

Jun 26, 2025 at 02:35 am

zkLend, a Starknet-based lending protocol, is shutting down after a $9.5 million exploit and ZEND token delistings. Treasury funds will compensate affected users.

Another one bites the dust in the wild west of DeFi. zkLend, a lending protocol built on Starknet, is calling it quits after a devastating exploit earlier this year and subsequent market pressures. Let's dive into what happened.

The Downfall: Exploit and Delisting

Back in February, zkLend suffered a $9.5 million exploit due to a precision rounding flaw. Ouch! If that wasn't bad enough, crypto exchanges Bybit and KuCoin then delisted zkLend's native token, ZEND, further crippling the protocol's liquidity. The double whammy of the exploit and delistings proved too much to handle.

The Inevitable Shutdown

On June 25th, zkLend officially announced it would be winding down operations. The team cited eroded user confidence and the liquidity crunch as the primary reasons for the shutdown. It seems like a recovery was just not in the cards.

What's Next for Users?

zkLend isn't leaving users completely high and dry. The remaining $200,000 in the treasury will be used to compensate users affected by the exploit. The DeFi Spring, recovery, and kSTRK portals will remain online, allowing users to unstake assets and claim balances. They are also retaining a security firm to trace any remaining stolen coins, and will route future recoveries to the user fund.

Open Source Future

In a move that’s both generous and forward-thinking, zkLend plans to release its codebase as open-source. This allows other developers to build upon their framework. It's like saying, "Hey, we messed up, but maybe someone can learn from our mistakes and create something even better!"

A Wider Trend: Crypto Hacks on the Rise

zkLend's story is a stark reminder of the risks in the crypto space. Crypto hacks are on the rise, with billions of dollars stolen in recent years. Smaller projects are particularly vulnerable, as an exploit can quickly lead to a death spiral.

Personal Thoughts

It's always sad to see a project go under, especially when it's due to a security breach. The zkLend team tried to do the right thing by compensating users and open-sourcing their code. Hopefully, other projects can learn from zkLend's experience and prioritize security above all else.

The Bright Side

Hey, at least they tried! The world of DeFi is a constant experiment, and not every project is going to succeed. But that's how innovation happens. Plus, who knows? Maybe someone will take that open-source code and build the next big thing. So long, zkLend, and thanks for the lessons!

Disclaimer:info@kdj.com

The information provided is not trading advice. kdj.com does not assume any responsibility for any investments made based on the information provided in this article. Cryptocurrencies are highly volatile and it is highly recommended that you invest with caution after thorough research!

If you believe that the content used on this website infringes your copyright, please contact us immediately (info@kdj.com) and we will delete it promptly.

Other articles published on Jun 26, 2025