Paradex Rollback Timeline: Database Migration Error Leads to Large-Scale Liquidation, Perp DEX Centralization Risk Exposes Concerns

BlockBeats News, January 20th. In the Starknet ecosystem, Perp DEX Paradex announced temporary maintenance yesterday. Despite the protocol not being brought online as expected after the completion of the maintenance, there were rumors in the community of a major vulnerability in the protocol. As a result, some users' perpetual contract trades were liquidated due to abnormally high funding rates.

Paradex's official announcement around 3:00 PM cited a system outage due to database maintenance/migration issues, leading to anomalies such as BTC price going to zero and triggering a large number of liquidations. They stated that the chain state would be rolled back to block 1604710 (UTC time 04:27:54) to restore the pre-database maintenance state, which is the last known correct state.

Paradex's official website finally resumed operations yesterday evening at 20:13.

The crypto community erupted in widespread skepticism and criticism towards Paradex's rollback, questioning the on-chain DEX's "reliability," especially regarding the security and true decentralization of the L2 architecture Perp DEX. Some community opinions suggest that Perp DEX might have been the "wrong product form" from the start, and in extreme situations, centralized control often reemerges under the guise of "fixing the system."

A viewpoint from Solana community member chase.skr garnered significant agreement, stating that Solana's more decentralized validator set has prevented the chain from unauthorized rollbacks, updates, or closures due to hacks or contentious forks. Consensus is essential, and centralized control of a blockchain is detrimental. The true decentralization of the "D" in DEX is worth reconsidering.