How to beat TradeXYZ
Source: http://x.com/i/article/2070845522508910592
First, some hard realizations:
- Shoku is more competent than you and a trillionaire, you'd be retarded to deny this.
- USDC was always king. Max & co were a sacrifice.
- All of the HIP-3 deployers up until now were running a broken strategy.
- long tail itself not a strategy, it's hiding in markets without demand.
Calling HIP-3 a structural monopoly because 3 teams deployed
$TSLA at the same time and the one with the most money won, is cope.
HIP-3 V2
The next step for HIP-3 is moving beyond markets that are already traded in TradFi. Using perps to build net-new markets for hard-to-price real-world cost exposures with latent hedging demand. To do this requires manufacturing oracles that TradeXYZ won't be able to easily move into, and are clean enough representation of real-costs to bring on real hedging volume.
First, recognize that no Hyperliquid eco team (or team in crypto) sizes up to the caliber of Hyperliquid Labs or Shoku&Co. The first step is acceptance. There is no shame in this, myself included. I dedicate 18 hours of my day for the last 2 years to Hyperliquid but never would I put myself in a position to directly compete against Jeff&Shoku for market share. You and any sized army will never win on resources or talent. "Jeff favors Shoku" is not why you will lose.
Second, understand what a moat is.
Every HIP-3 deployer assumed that being first was enough.
It is not.
- Jeff will own the perpetual swap on everything that can be classified as a crypto asset.
- Shoku will own the perpetual swaps on every other asset that has an easily understood pricing function.
Every data source that has a price tag for a license, and can be directly plugged in to a perps market with reasonable demand, will be owned by TradeXYZ. Existing public markets across all jurisdictions. No exceptions.
If you launch something that can be copied, it will be copied and dominated by TradeXYZ as soon as it finds PMF as a perp. Simple. Liquidity begets liquidity; but no matter how early you launch - Trade will out-liquidity you when it matters.
The key is data that is easy for a very specific/niche (but valuable) liquidity profile to understand, but way too domain specific for any general exchange deployer to keep up with and replicate effectively.
Why most deployers lost
Oracles are a hard problem, and that is the structural issue with HIP-3.
Non-Trade deployers lost for three reasons:
- They standardized around familiar Pyth/Seda feeds to attract market makers.
- That standardization outsourced their core IP to oracle providers.
- Once a market showed demand, TradeXYZ could replicate it with better liquidity.
The result: deployers optimized for easy liquidity and accidentally destroyed their reason to exist.
Every losing HIP-3 team was told by the top Market Makers that they would only make their markets if they used standardized Pyth/ Seda oracles / data feeds. From the perspective of an MM - demanding standardization is entirely fair.
The oracle is the risk asset on a HIP-3 DEX; but it also is the product.
There is a structural conflict: being creative with oracles kills important integrations & access to easy liquidity, but being uncreative with oracles kills your purpose of existence entirely.
All non-Trade DEXes were standardized on familiar Pyth Seda oracles/data feeds in a pursuit of attracting the advertised liquidity providers. This killed them.
Any new market that was developed, outsourced the critical IP to Pyth/Seda; which could be freely re-sold / replicated across deployers with ease. Oracle providers are in the business of selling the exact data layer you are building on to anyone willing to pay for it.
How would any HIP-3 deployer create a moat under this structure?
Creativity was lost in an effort to attract already existing HIP-3 volume, there has been no valid attempt to attract new volume. All non-Trade DEXes were pushed to deploy well understood markets with known hedging volume.
You only deploy where the existing HIP-3 volume was willing to run a basis trade, perps on liquid TradFi markets. Not creating new volume/demand. Any new market that was developed was just a data feed to an existing TradFi exchange (which TradeXYZ has tools to outcompete you on).
Why the exceptions failed
There were a few respectable yet failed attempts at developing novel oracles for non-replicable prices feeds:
- non-standard oracles meant the usual name MMs would not market-make.
- complex and experimental oracles meant the net-new volume was scared by risk that was hard to understand, trade, and integrate.
- eventually had their lunch eaten by TradeXYZ if they targeted markets worth dominating and easy to price.
Ventuals is a great example here:
- Trading Ventuals markets was trading in-house experimental oracles actively in development. Markets attractive in theory became a "how is it priced under the hood" complexity issue for institutional volume.
- Pre-IPO becomes easy to price when it matters the most: right before IPO (hyperps). So TradeXYZ was happy to come dominate at the most critical moment.
This is the worst possible market profile: expensive to build first, low-demand while early, and cheap to replicate once demand finally appears.
Who has actually made money on HIP3
The winners of HIP-3 today:
- Hyperliquid x TradeXYZ
- Standard Oracle Providers (Pyth, Seda)
- staked HYPE providers (Valantis)
- Market Makers selling liquidity
The losers:
- Every HIP3 deployer except TradeXYZ
How to win as a HIP-3 Deployer in 2026
There exists a design space of oracles valuable enough to hedge, hard enough to price, and niche enough that TradeXYZ will not immediately prioritize them.
This is not a general basket of "long-tail", it's a carefully crafted and well executed list of untapped addressable markets. It takes focus and a strict lack of generality for any team to execute on this.
The edge is markets that have hedging demand, but are not straight forward to price. Ideal market have a concentrated set of actors that want to be able to hedge their exposure, but their exposure is not traditionally priced as liquid instruments today. Creating new financial markets to service unserviced cost-speculation demand, uniquely unlocked by perps.
Example:
- basket of firms with complex but shared exposure across regional energy sources, GPU rental prices, inference costs, etc.
- basket of firms with complex but shared exposure across regional shipping costs, oil prices, manufacturing output across specific regions.
The edge is designing hedging instruments for large firms with unserviced demand for markets that represent their direct costs. Basketting their exposure as directly as possible and much more efficiently than any existing TradFi instrument.
Ex: BTC Miner Perp = weighted basket of important regional energy prices + hashprice/hashrate + ASIC financing/rental costs.
This is new volume that perps uniquely unlock, not TradFi volume that it can port over.
The exposure should be niche enough to attract a new set of hedging volume, but general enough to be something worth gambling on
- a defacto representation of memory demand or ai-inference cost
- a defacto representation of X supply chain throughput
The niche is that the basket is engineered to address the real hedging exposure that price-exposed institutions have, while being general enough to fit a narrative tradeable by everyone else.
This is fundamentally different than US ENERGY perps or H100 Perps. It's way more handcrafted to the exposure of firms that we want onboarded as hedging volume: commodity producers, datacenter, bitcoin miners, XY&Z manufacturers.
This requires a HIP-3 deployer to be on the ground across a set of non-financial industries marketing their perps as direct hedging instruments to the direct costs of real firms. Integrating & weighting the exact data sources that affect their costs - not general proxies.
General long-tail deployers will die harder than general short-tail deployers.
The goal is to form oracle re-implementation barriers large and layered enough where TradeXYZ won't be able to contact Pyth or spend a weekend writing an oracle implementation to eat your lunch the day your volume picks up.
The next winning HIP-3 deployer will not copy TradFi markets onto perps. It will create new markets for risks that finance does not currently service.
Build the demand yourself. Build the oracle yourself. Make the market cheap to understand for a very target liquidity profile, and harder to replicate for anyone outside this circle.
More soon.