⚠︎ Risk warning: leveraged derivatives on unregulated platforms — you can lose everything you deposit. Not investment advice.
Perp DEX Safety: What's Risky, and Who's Had Problems
"Is it safe?" doesn't have one answer for a perpetual DEX, because the risk lives in several independent places. Trading from your own wallet removes one class of danger — no company can freeze your account or lose your deposit in a bankruptcy — but it does not make a venue risk-free. The contracts, the price feed, and the people who can change them all still matter. This page breaks down the categories that actually decide safety, then tracks the concrete incidents we've verified on the venues we cover.
The four risks that matter
- Custody & upgradeability. Self-custody only protects you if the contracts holding collateral can't be changed out from under you. Several venues let a single key upgrade core contracts with no delay or exit window — which means that key (or whoever compromises it) can, in principle, move funds. This is the single biggest variable between "self-custodial" venues.
- Oracle & price-feed integrity. Perps are priced off an oracle. If that feed can be spoofed or a signer key is compromised, an attacker can print a false price and drain the pool that backs trades — this is the mechanism behind several of the largest perp-DEX losses.
- Off-chain components. Order-book and "CEX-speed" venues often match or sequence off-chain, then settle on-chain. That's a trust assumption: an outage or bug in the sequencer can halt trading or misprice positions, even when custody is on-chain.
- Liquidity & token risk. Thin liquidity turns a large exit into a crash; a venue's own token falling sharply doesn't drain your collateral but is a signal about the health of the ecosystem you're trading in.
Incident & risk tracker
Verified, dated, and sourced — reviewed as of 2026-10-07. Venue reality changes after a page is published, so we keep this in one place and cite the primary report for each item; always check a venue's own channels for its current status before trading.
Ostium — Rebuilding
Security incident — trading was paused
An attacker used a compromised oracle signer key to push falsely authorized price reports through Ostium's price-feed automation, draining 23,752,746 USDC (~$23.75M — Ostium's own final accounting; earlier estimates ran $18M–$22M) from the Ostium Liquidity Pool via roughly 20 looped open-and-close trades. Trader collateral sits in a separate, isolated contract and was not affected, per Ostium's statement. Trading was paused within about an hour of the exploit.
Trading re-enabled in stages
Ostium reopened trading in stages from 2026-07-23, restoring risk-management and reduce-only actions first; open positions carried over and were marked to the live market at reopen. Ostium's post-mortem, published 2026-07-30, confirms the $23.75M figure and the compromised off-chain price-feed signer as root cause and states trader margin was never touched.
LP recovery plan published — Stage 2 still undefined
On 2026-09-30 Ostium published a two-stage recovery plan for the 3,666 wallets that lost money in the OLP vault, per The Defiant. Stage 1 repays the 3,321 wallets that lost $1,000 or less in full through a "Convenience Recovery Contract" — at most $3.32M of the $23.8M taken. The other 345 wallets choose between a $1,000 payment and a pro-rata share of Stage 2, which Ostium says it will fund from funds recovered from the attacker (649,967 USDC so far), a share of protocol revenue and "potential further benefits"; it has not set out the revenue share, the election deadline or what those benefits are. The OLP share price stood at 0.337 USDC against 1.10 before the attack, per the vault contract as reported. Treat the larger-LP side of the loss as unresolved until Stage 2 is defined. Ostium's docs (re-read 2026-10-07) describe OLP deposits settling daily with no pause notice; we have not confirmed deposit availability in the app.
edgeX — Operational
edgeX V1 contract frozen — trading had moved to V2
edgeX's original V1 deployment — a StarkEx Validium on Ethereum, whose critical contracts L2BEAT rates as upgradeable by a single externally-owned account, with no window for users to exit before an unwanted upgrade, and which has an address with unverified source code — froze on 2026-08-14, per L2BEAT, after a forced withdrawal on Ethereum went unprocessed for seven days. L2BEAT describes it as a planned sunset: trading had already moved to edgeX V2 on EDGE Chain in May 2026. L2BEAT's change log records that contract's isFrozen value flipping from false to true, and an on-chain read of the V1 StarkPerpetual contract (0xfAaE…7d83DD) still returned true on 2026-10-07. L2BEAT's edgeX page tracks that V1 deployment, so its risk ratings describe the frozen system rather than V2. edgeX's live V2 market API (edgex-prod-v2.edgex.exchange) listed 183 contracts, all open for trading, on 2026-10-07; this is a standing disclosure for anyone with history on V1, not an outage of the live venue.
dYdX — Operational
Most of its markets wound down in 2026 — 73 active, 223 in final settlement
Since February 2026, dYdX governance has retired inactive perpetual markets in scheduled batches: a wind-down proposal on the community forum in every month from February to September, put to an on-chain vote within days. All twelve batches proposed from February to September — 181 markets in total — now show as final settlement on-chain. The latest, posted 2026-09-25, moved five — ARKM, SHIB, WOO, XPL and ZRO — to final settlement on its stated 2026-10-02 schedule after each failed a $100 market-order slippage test (~30%); the August batch moved 21 (SNX, GRT, MANA, CRO, ETHFI, MNT, STX, AXL and ZK among them) on 2026-09-04. dYdX's own indexer listed 73 ACTIVE markets against 223 in FINAL_SETTLEMENT on 2026-10-07 (78 and 218 on 2026-09-16); our own snapshot of dYdX's active listings held 113 entries on 2026-07-30 and 99 on 2026-09-02. Per dYdX's help center, when a market is wound down all open positions are closed automatically through deleveraging and the order is displayed as final settlement — so confirm a pair is still listed before planning a dYdX position. The batches used failed $100-market-order slippage tests (over 5%), near-zero monthly volume and 30+ days without a trade as their criteria, so a dYdX market that looks like that is a delisting candidate; the delisting framework notes that retired markets can be listed again later.
Paradex — Operational
Past incident: funding-index outage and chain rollback
On 2026-01-19 a database-maintenance race condition zeroed Paradex’s funding indices, briefly pricing BTC at $0 and triggering mass liquidations; the site was offline for roughly six hours. Paradex rolled the chain back to block 1,604,710 and refunded about $650,000 to roughly 200 affected accounts. The venue has operated normally since — noted here as resolved context for anyone weighing its reliability, not a current outage.
No entry for a venue means we have not verified an incident or standing custody flag for it — not a guarantee of safety. Absence of a report is not proof of soundness.
When the venue is fine but your wallet is not
Most losses that reach the community channels are not protocol hacks. They are wallets that signed something they should not have, or keys that left the device. Hyperliquid's own support page puts it plainly: if you see unauthorized transactions or missing funds, "your wallet was likely compromised. Hyperliquid is non-custodial," so the venue cannot reverse it (Hyperliquid docs). Every venue here works the same way. The patterns below are the ones official sources describe, read on 2026-09-29.
- Signature phishing. A fake site asks for a signature rather than a transaction. MetaMask defines it as "a method where attackers obtain an off-chain signature from users, and then use it later to steal their assets" (MetaMask help centre). Scam Sniffer's 2025 report counts $83.85M lost across 106,106 victims to this class, with Permit signatures the main type (Scam Sniffer, January 2026).
- Infostealer malware. A joint FBI and CISA advisory on the LummaC2 infostealer says it can take "cryptocurrency wallets, browser extensions" along with passwords and session data from an infected machine (CISA advisory AA25-141B, May 2025). A browser-extension wallet is only as safe as the computer it runs on.
- Fake support. Hyperliquid says support happens only in a ticket inside its own Discord, and that "if someone directly reaches out to you, assume they are a scammer" (Hyperliquid support guide). No venue here needs your seed phrase to fix anything.
- Trading keys you forgot you approved. Perp DEXs let you approve a separate key to trade for you. On Hyperliquid a master account "can approve API wallets to sign on behalf of the master account or any of the sub-accounts" (API wallets); a builder fee, by contrast, "must be signed by the user's main wallet, not an agent" (builder codes). Lighter's API keys are "used to sign requests when interacting with the exchange" (Lighter docs), and Paradex documents an endpoint to "revoke a subkey for the authenticated account" (Paradex docs). Bots, copy-trading tools and terminals all ask for one of these. Know which keys are live on your account and remove the ones you no longer use.
If it already happened, Hyperliquid's checklist is the right model for any venue: "Stop using the compromised address. Treat it as permanently unsafe." It goes on to create a new address "using a trusted wallet provider", move what is left, revoke contract permissions with revoke.cash, clear browser cache and cookies, and "determine if your device has malware" before trusting it again. Hyperliquid also supports native multi-sig for accounts that hold more than you would want one key to control (multi-sig). Reports of a drain posted in community forums are useful warnings but rarely establish how it happened; this page does not treat them as evidence.
When the venue itself shuts down
Self-custody keeps a company's bankruptcy away from your collateral, but it does not keep a venue open. Three closures announced in 2026 show how it plays out, and each gave users a deadline rather than an open-ended exit.
- Satori Finance, a perp DEX, said on 16 June 2026 that "our revenue has not been sufficient to sustain operations" and opened a withdrawal and position-closing window to 16 July, 23:59 UTC. After that, it warned, "you may no longer be able to withdraw assets remaining on the platform" (Satori Finance on X).
- Dango, a perp DEX on its own L1, said on 24 July 2026 that trading would halt on 29 July at 12 pm UTC and "Remaining positions will be closed at oracle price"; on 13 August "the Dango L1 blockchain will stop running", with "Deposits not withdrawn at this point" refunded to their deposit addresses on Ethereum. The same notice said "Limits to withdrawals will be lifted shortly" and warned users to "Be careful of slippage, as liquidity is expected to be thin" (Dango on X).
- BitMEX, a centralized exchange that says it "invented the 100x leverage perpetual swap", announced on 23 July 2026 that it would close on 23 September at 04:00 UTC. From 26 August users could only reduce positions, and it said it would "force close existing open positions to ensure an orderly wind down of the market". KYC'd users who leave assets behind are charged "an account fee of 1% per annum (charged monthly), or USD 50 equivalent" for small accounts. On 23 September it said trading, deposits and new positions had ended and "Login and withdrawal capabilities remain available" (BitMEX, 23 July; 23 September).
The sequence was the same on both sides of the custody line: a notice, then a window to close and withdraw. At Dango and BitMEX, whatever was still open after that was closed for the user at a price they did not choose. What differed was what happened after the deadline. BitMEX keeps processing withdrawals after closing but charges for balances left behind; Dango sent funds still on its chain back to Ethereum deposit addresses; Satori said assets left after its window might not be withdrawable. Among the venues this site covers, dYdX governance has moved most of its markets to final settlement during 2026 while the venue keeps running (see the tracker above). If a venue you use announces a wind-down, close positions before its forced-settlement date, withdraw early, and treat any offer of a faster exit as phishing: BitMEX's notice says "no such expedited service is available".
How to vet a venue yourself
- Check L2BEAT for the custody/upgradeability risk of any venue that runs as an L2 or validium — it flags whether contracts can be upgraded by a single key and whether there's an exit window.
- Read the audit, not the "audited" badge. Confirm a real firm audited the current contracts, and skim the findings — an old or scope-limited audit is weak assurance.
- Look at the venue's own status page and socials before depositing during any period of unusual volatility; halts and post-mortems appear there first.
- Size to what you'd accept losing. Every venue here can fail in a way that is out of your control; position accordingly.
FAQ
Is any perp DEX completely safe?
No. Self-custody removes counterparty/custodial failure, but smart-contract bugs, oracle manipulation, upgradeable contracts, and off-chain-component outages remain. "Safer" is the honest framing, not "safe."
Does self-custody mean my funds can't be taken?
Not on its own. If the contracts holding collateral are upgradeable by a single key with no exit window, that key is a single point of failure regardless of self-custody. That's why custody/upgradeability is the first thing to check.
My funds left my Hyperliquid account and I did not do it. Can the venue refund me?
Almost certainly not. The venues here are non-custodial: an action signed with your key or an approved trading key is final. Follow the checklist above, move what remains to a new wallet, check the device for malware, and report theft to your local police or national cybercrime unit.
Which venues here have had incidents?
The tracker above currently lists Ostium, edgeX, dYdX and Paradex, each with its status, whether the notice is resolved, and a link to its primary source. For venues that closed outright in 2026, see when the venue itself shuts down.