Starknet perpetual DEX faces maintenance issues, users are forcibly liquidated due to abnormal fees

2026-01-19 06:50:16

Abstract generation in progress

【Blockchain Rhythm】The perpetual derivatives DEX project in the Starknet ecosystem suddenly announced a system maintenance, but the situation is a bit troublesome— the maintenance period has already exceeded the limit, and the protocol has still not resumed operation.

Even worse, community users encountered problems during the platform recovery. Many traders’ perpetual contract positions on the platform were forcibly liquidated due to the funding rate soaring to abnormal levels, resulting in significant losses for users.

The project itself is a good concept—combining institutional-grade liquidity resources with DeFi transparency and self-custody features on a Layer2 application chain, built using Starknet developer tools. It is said to be the result of a six-month in-depth collaboration between a well-known infrastructure team and a liquidity platform. However, based on the current situation, system stability remains a major challenge.

View Original

This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.

12 Likes

Reward
12
6
Repost
Share

Comment

0/400

ChainComedian

· 3h ago

Hey guys, maintenance overdue and still causing liquidations, this operation is really top-notch --- Is it another half-year result from the "well-known infrastructure team"? I don't believe you --- Rate spikes causing forced liquidations... isn't this just the daily routine of contract exchanges? --- Layer2 should be stable, why is it still as sluggish as L1? --- So now, is there anyone responsible for the money lost, or are they just brushing it off? --- Perpetual DEX maintenance overdue, hearing about this so often it no longer surprises me --- Institutional-level liquidity, transparency, self-custody, feels like these buzzwords are overused --- How did the community react when users were forcibly liquidated? Is there any compensation? --- Starknet ecosystem has another issue, honestly I can't tell when these projects will finally be reliable

View OriginalReply0

ApeWithNoFear

· 3h ago

Maintenance overdue can still harm users, is this what they call "deep cooperation成果"? Laughing to death --- Once again, abnormal forced liquidation due to funding rate, I've seen this trick too many times --- Layer2 application chain stability is like this, what are we talking about institutional-level liquidity... --- Half a year of cooperation and this is the result, might as well go back to CEX directly --- Rate surge leading to forced liquidation? Feels like a system bug wasn't handled properly --- Starknet ecosystem has issues again, when will it finally settle down --- Really outrageous, how does maintaining a system harm user assets --- The protocol hasn't resumed and is still charging fees, this logic is unparalleled --- So who should be responsible for users' losses, is there any statement? --- DeFi transparency can't prevent such basic mistakes

View OriginalReply0

Whale_Whisperer

· 4h ago

Maintenance overdue and still爆雷, is this what they call institutional-level liquidity? Laughable, my stablecoins in my wallet are still more stable. --- It's the old trick of rate spikes forcing liquidation again. What’s the result of deep cooperation? This? --- What's going on with Starknet? It feels like every project is causing trouble. --- Abnormal funding rates leading to forced liquidation— isn’t this just sneaky rug pulling? Playing these tricks even during maintenance, truly impressive. --- Speaking of which, doing perpetuals on layer2 application chains is already risky, and now adding the system stability pit? I really dare not touch it. --- Protocol recovery is indefinite, users lose everything— is this the democracy of web3? --- Half a year of cooperation and they come up with this? Still too inexperienced. --- At the moment of rate spike, how many people were forced to go all-in? Someone has to be responsible for this. --- Machine learning failed to maintain, but instead dug a hole— a bit outrageous.

View OriginalReply0

NFTregretter

· 4h ago

Maintenance overdue, the fee rate is crazy, leading directly to liquidation. Is this the daily routine of the Starknet ecosystem? Another "deep cooperation" that ends in failure; no matter how nicely it's written, it can't hide the system's fragility. L2 was supposed to be the savior, but it started hurting people before even launching, it's hilarious. When will these issues finally settle down? It's really getting on my nerves. Such a basic mistake as abnormal fee rates can happen—what about institutional-level liquidity? Just bragging? Users suffer huge losses, while the project team is carefree—just maintain it, no need to worry about losing money. Here we go again, I have to ask, who still dares to use Starknet's derivatives?

View OriginalReply0

CryptoDouble-O-Seven

· 4h ago

Maintaining overdue positions can still trigger liquidation, this operation is incredible. Where is the institutional-level liquidity promised? How can the fee rate skyrocket like this? It feels like a joke.

View OriginalReply0

DefiOldTrickster

· 4h ago

Haha, maintenance overdue and the rate skyrockets. I've seen this trick since 2016—a textbook example of forced liquidation. If you don't understand how to operate in a production environment, don't boast about "institution-level liquidity." And where's the promised half-year cooperation? How can these people still not learn? Abnormal funding rates? Bro, I just want to ask, did the clearing engine eat shit? Another "deep cooperation achievement" crashes spectacularly, hilarious. It's truly outrageous that Layer2 can still be manipulated like this. Here's the question: who will cover this loss? Really, every time it's just an excuse for maintenance, but in reality, it's just naked shorting. I want to see what on-chain data has to say. My five-year-old veteran intuition tells me there's probably a story behind this.

View OriginalReply0