Over the past week, a protocol lost its entire team—and barely anyone noticed. Ventuals, a pre-IPO perpetuals venue built on Hyperliquid, announced its closure on February 10. The market yawned. Three days later, separate announcements confirmed that Ventuals co-founders Alvin Hsia and Emily Hsia, along with at least three engineers, would join Phantom. The market still yawned. But for those who parse the signal from the noise, this is not a routine hire. It is a strategic declaration of war.
I have spent the last eight years auditing smart contracts, tracing invariants, and watching human capital flow where the real value lies. What I see here is a shift from application-layer specialization to infrastructure-layer absorption. Phantom—the dominant Solana wallet with a >60% estimated market share—is not just adding employees. It is acquiring the tacit knowledge required to build a battleship-grade perpetuals engine. This is the kind of move that rewrites competitive maps.
Let me ground this in context. Phantom currently makes money through swap routing fees, fiat onramp commissions, and the occasional strategic partnership. It is a non-custodial wallet: users hold their own keys, and Phantom executes swaps via aggregators like 0x or Jupiter. It has never run a matching engine, never liquidated a position, never calculated a funding rate. Ventuals was the opposite. It operated a venue on Hyperliquid where traders could speculate on pre-IPO stocks—SpaceX, Stripe, the usual unregistered securities—via perpetuals. That is a high-regulatory-risk, high-technical-sophistication business. Ventuals built it, ran it, and likely shut it down because the compliance costs exceeded the revenue. Their team now brings that expertise to Phantom.
The core technical question is straightforward: how do you embed a perpetuals exchange into a non-custodial wallet? The naive answer is to route orders to Jupiter Perps or Hyperliquid. But that turns Phantom into a thin UI—no margin control, no liquidation logic, no unique value. The ambitious path is to build a closed-loop system: an on-chain order book (or virtual AMM), a custom oracle suite, a liquidation engine, and a risk management framework that operates within the wallet's smart contract boundary. That is what Rabbit Wallet attempted, and what Jupiter Perps solved via aggregation.
From my experience auditing the Lido stETH–Aave composability vulnerability in 2021, I know that adding a leveraged trading module to an existing system creates hidden dependencies. In that case, Lido's node operators could censor stETH transfers, violating Aave's permissionless assumption. Here, the critical dependency is liquidation. In a non-custodial wallet, who triggers liquidations? If Phantom runs a centralised liquidation bot, it becomes a single point of failure—and a regulatory target. A decentralised liquidation mechanism, say via keeper networks, adds gas cost and latency. That is the trade-off matrix Phantom must solve.
Ventuals team brings firsthand knowledge of Hyperliquid's architecture: its order book, its funding rate mechanics, its latency profile. When I traced the Uniswap v1 invariant manually in 2019, I learned that subtle bugs in mathematical functions—like integer overflow in eth_to_token_swap_input—can go unnoticed by automated tools. Ventuals likely found and fixed similar low-level issues on Hyperliquid. That kind of intuition is not something you can hire from a job board. It comes from months of staring at liquidation events and gas spikes during Solana congestion.
Now the contrarian angle. The consensus narrative is that Phantom will leverage its massive user base to dominate Solana Perps. I am not convinced. User base alone does not equal trading volume. Most wallet users perform simple token swaps—they are not leveraged traders. The retention rates for perpetuals platforms are abysmal; 90% of retail traders lose money and churn. Phantom's current revenue model is stable because swaps are low-risk. Introducing Perps introduces a volatility in revenue that depends on trading churn—and churn happens when users get liquidated, which erodes trust. Moreover, Ventuals' own failure on Hyperliquid suggests that even a well-built venue cannot survive if liquidity is thin and regulatory pressure is high. Why would embedding the same engine inside a wallet change that?
Zero-knowledge isn't mathematics wearing a mask; it is a trust assumption. And right now, Phantom's new Perps will likely be closed-source initially, demanding trust from the same users who chose the wallet for its non-custodial ethos. That is a blind spot. The market doesn't care about your protocol's elegance, only its liquidity. Jupiter already has deep liquidity from aggregating multiple sources. Hyperliquid has its own L1 and token. Phantom will have to bootstrap liquidity from scratch—either by offering incentives to market makers or by routing to Jupiter as a backend, which undermines the integration.
Code is law, but bugs are reality. Phantom's biggest risk is not technical failure—it's regulatory. Ventuals' pre-IPO product was a regulatory grey area that likely forced its shutdown. If Phantom inherits that team's mindset, it might be tempted to recreate similar products. That would be a mistake. The CFTC and SEC are watching wallet-based Perps closely. The smart move is to launch only standard crypto perpetuals (BTC, ETH, SOL) and avoid equities entirely. Whether the team has the discipline to do that remains to be seen.
Takeaway: Watch for Phantom's beta launch in Q2 or Q3 2026. If they deliver a seamless, low-slippage experience with transparent liquidations and no regulatory shortcuts, they will become a formidable competitor to Jupiter and Rabbit Wallet. If they stumble on latency or succumb to the temptation of pre-IPO derivatives, they will repeat Ventuals' failure—this time with a much larger audience. The next six months will determine whether wallets become the new exchanges or remain just interfaces to someone else's liquidity.