May 10, 2025
11 11 11 AM
Latest Post
Lido Proposes a Bold Governance Model to Give stETH Holders a Say in Protocol Decisions State of Crypto: Mapping Out the Senate Stablecoin Bill’s Next Steps Analysis: Coinbase Is Buying Bitcoin, Just Don’t Call It a Treasury Strategy. Dogecoin Surges 10%, Bitcoin Nears $104K Amid Renewed ‘Risk-on’ Sentiment As Meta Said to Mull Tokens, Senator Warren Calls for Blocking Big Tech Stablecoins Bitcoin Miner MARA Stock Surges Despite Earnings Miss as Analysts Applaud Cost Cutting Trump Family Profited $320M on Memecoin Despite 87% Decline Since Day One CoinDesk Weekly Recap: Even ETH Is Up Samourai Wallet Prosecutors Say Delayed FinCEN Disclosure Wasn’t a Brady Violation Coinbase Draws Mixed Reviews From Wall Street After Q1 Earnings Miss, Deribit Acquisition

ZKsync Sunsets Liquidity Rewards Program, Citing Bearish Market Conditions

Layer-2 network ZKsync has announced that it will be sunsetting the Ignite Program, which rewarded users for providing liquidity, due to bearish market conditions.

“After careful consideration, the DeFi Steering Committee (DSC) has decided to not renew Ignite for Season 2 and will be sunsetting the program starting March 17th, 2025 by turning off rewards for period 6,” ZKsync posted on X.

It added that the long-term vision is centered around the Elastic Network, which is composed of multiple chains within the ZKsync ecosystem.

“Unfortunately we’re navigating a bearish market right now. In line with many other ecosystems, ZKsync has decided to be more conservative with spend in the short to medium term in response to these evolving conditions,” it added. “To stay sustainable, we’re tightening our focus and spending smarter, rather than fighting headwinds.”

Total value locked (TVL) on ZKsync is down by around 50% since Jan. 30 as the wider crypto market is grappling with a correction that has seen bitcoin and ether lose 13% and 27% of their respective market caps in the past month.

ZKsync’s native token (ZK) has plunged by 35% in the same period.

This post was originally published on this site