The HyperEVM Ecosystem Map
HyperEVM applications cluster around lending, liquid staking, AMMs, vaults, options, structured products, data, wallets, and infrastructure, with many of them using HyperCore liquidity or HYPE as an underlying primitive.
The HyperEVM ecosystem is best understood by function rather than by a long list of project logos. Lending protocols create credit, liquid staking protocols transform staked HYPE into composable assets, AMMs create EVM liquidity, vaults package strategies, derivatives applications add options and structured products, and infrastructure projects connect users to both HyperEVM and HyperCore. The common thread is proximity to HyperCore's native financial state.
Credit and lending
HyperLend, Morpho deployments, Felix, and other lending surfaces let users supply assets, borrow, and construct leverage on HyperEVM. Their smart-contract risk and liquidation logic remain separate from HyperCore Portfolio Margin even when strategies move assets between the two.
Liquid staking and productive HYPE
Kinetiq and staked-asset infrastructure such as Valantis-linked markets make validator delegation more composable. The underlying yield originates from native HYPE staking, while receipt-token liquidity and smart contracts add a second risk layer.
Liquidity and AMMs
HyperEVM AMMs serve token pairs and use cases that do not belong in native HyperCore order books. Some are purpose-built for correlated or staked assets, while others provide broader spot liquidity.
They coexist with HyperCore CLOBs rather than replacing them.
Options, vaults, and structured products
Protocols such as Derive, Rysk, Veda-powered vaults, and strategy platforms build payoff structures on top of spot, perp, staking, and lending primitives. These products can combine multiple risk engines, making mechanism-level explanations more useful than category labels.
Data and infrastructure
RPC providers, wallets, explorers, analytics tools, bridges, and indexers are the operational layer that makes the ecosystem usable. Hyperliquid's own documentation points to community-maintained directories rather than presenting one permanent canonical app list.
That means an ecosystem map is inherently time-sensitive and should be review-dated.