Researcher compares four perpetual DEXs after Binance hot wallet theft, says only Lighter could block server-side fund drains

Researcher compares four perpetual DEXs after Binance hot wallet theft, says only Lighter could block server-side fund drains

N
News Editor
2026-11-02 17:58:14
A post by researcher jaehaerys on X examined the contract architecture of four perpetual decentralized exchanges — Lighter, Hyperliquid, Aster, and Variational — after the Binance hot wallet theft. The review asked a narrow but practical question: if a protocol’s internal systems were compromised in a similar way, could users still rely on the contracts to keep funds safe or exit without the team. Among the four, jaehaerys said only Lighter had a withdrawal design that could stop an attacker from directly draining user balances, because standard withdrawals are tied to the wallet used for the first deposit and require ZK proof verification. The protocol also includes a forced withdrawal path that can trigger a full exit after 14 days. The other three protocols, in his view, still depend heavily on custodial or operator-controlled structures. He said 86% of Hyperliquid’s roughly $6.5 billion in USDC sits in a Coinbase single-key wallet, while Aster requires operator-initiated withdrawals and Variational allows any one of 17 operational keys to move USDC from any pool. His broader point was that a DEX label does not by itself guarantee user fund safety.

After the Binance hot wallet theft, researcher jaehaerys posted a breakdown on X of the contract structures behind four perpetual DEXs: Lighter, Hyperliquid, Aster, and Variational. The question he focused on was simple: if a protocol’s internal systems were compromised in the same way, could users still get out safely, or could an attacker drain balances anyway.

His conclusion was blunt. Of the four, only one protocol could prevent an attacker from directly withdrawing user funds.

Four perpetual DEX designs under review

In the X thread, jaehaerys listed the rough scale of funds involved: about $1 billion for Lighter, about $6.5 billion for Hyperliquid, about $500 million for Aster, and about $290 million for Variational. His review did not center on whether the front end looked decentralized or whether trades were recorded on-chain. He looked at whether users could still protect their assets if the team’s systems were breached.

Lighter: tighter withdrawal controls and a forced exit path

Jaehaerys described Lighter as the design that comes closest to decentralization among the four. Withdrawals require ZK proof verification, and standard withdrawals can only be sent to the wallet address bound to the user’s first deposit. Under that setup, he said, a server compromise alone would not let an attacker move user balances out.

The protocol also includes a forced withdrawal mechanism. If a withdrawal is not processed within 14 days, anyone can trigger what he called “desert mode,” allowing all users to exit.

He did not present Lighter as fully trustless. Prices are still supplied by the operator, and a 3/5 multisig together with a 4/7 security council can change the code without notice.

Hyperliquid: 86% of USDC sits in a Coinbase single-key wallet

His critique of Hyperliquid focused on custody. According to jaehaerys, 86% of the roughly $6.5 billion in USDC is held in a single-key wallet under Coinbase. That means fund safety depends on Coinbase’s custody practices, and that part cannot be verified on-chain.

He also wrote that the Hyperliquid chain can execute system transactions without going through the Coinbase private key. On the validator side, five validators run by the Hyper Foundation account for 47% of staked assets, and the node software is closed source.

Aster and Variational: still custodial at the core

For Aster, he said each withdrawal must be initiated by an operator address and approved by two keys. In that structure, a user signature only proves that a withdrawal was requested; it does not protect the pool itself.

Aster does have an hourly withdrawal cap, but the same 4/7 multisig can immediately change roles and adjust the cap.

Variational, in his description, is even more permissive. Any one of 17 operational keys can move USDC from any pool, there is no amount limit in the contract, and users have no forced exit mechanism.

A DEX label is not a safety guarantee

Jaehaerys ended the thread with a broader warning. A perpetual DEX may have a decentralized front end and on-chain trading, but user funds can still remain under the control of team keys or operator addresses.

Before sizing up positions, he said users should verify two things: where the funds are actually held, and whether they can exit on their own if the team is unavailable. In his framing, contract permissions and exit routes matter more than the DEX label itself.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
9500

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.