Paradex, a perpetuals exchange built on Starknet, suffered a major pricing failure that briefly showed Bitcoin at $0 on the platform and set off a wave of automatic liquidations. After the incident, the exchange said on Discord that the issue was caused by an error during a database migration and that it would restore the system by rolling back to the last correct block before maintenance began.
Price glitch quickly turned into forced liquidations
Users on social platforms said Bitcoin suddenly dropped to zero on the Paradex interface before snapping back to normal. In that short window, the platform had already marked a large number of positions for liquidation and force-closed them.
One user said the move first looked like a display problem, but the situation appeared more serious after seeing Bitcoin fall to $0 and rebound almost immediately on desktop. According to that account, thousands of liquidations had already appeared on the platform.
Exchange traces the issue to database migration
Paradex later said it had identified the source of the disruption as a mistake during database migration. Engineering director Clement Ho said the system would revert to the last correct block before maintenance, at block height 1604710.
The rollback reaches beyond the liquidations tied to the faulty price. Under the plan described by the exchange, all trades, liquidations, deposits, and withdrawals processed during the affected period will be canceled, with the platform state restored to what it was before the failure. That may reverse wrongful liquidations, but it also erases profitable trades that were completed normally during the same window.
Rollback decision reopens debate over finality
In blockchain systems, rollback is widely seen as an extreme response because it rewrites states that had already been confirmed. Transaction finality has long been treated as a core property of onchain records.
The source material notes that when major networks or protocols face severe failures, the more common response is to halt operations or apply targeted fixes to contain damage, rather than reverse completed activity. Paradex's decision has put attention back on a familiar question: if a platform can cancel recorded history, how should its decentralization claims be understood?