The Yutu network
Yutu is an L2 built on Hyperliquid. The network runs its own consensus and execution while using HYPE for gas and maintaining direct economic and product links to Hyperliquid.
The chain supports two execution paths:
- Native protocol actions for trading, accounts, risk, and market state.
- EVM transactions for contracts, wallets, and applications.
Both settle into the same Yutu chain history and appear in the explorer.
Network components
| Component | What it does |
|---|---|
| Native perpetuals | Matches orders and records positions, collateral, funding, and liquidations |
| EVM execution | Runs contracts and standard wallet transactions |
| Write-precompile promises | Connects EVM contracts to native market actions with resolvable tickets |
| Hyperliquid market reads | Makes Hyperliquid prices and order-book depth available to Yutu applications |
| Bridge | Moves HYPE between Hyperliquid and Yutu |
| Explorer | Indexes blocks, transactions, addresses, accounts, events, and routed orders |
HYPE gas
Yutu doesn't introduce a separate gas asset. Contract calls, transfers, trades, and other network transactions pay gas in HYPE.
Applications should keep enough HYPE in the connected Yutu address to cover execution as well as any amount being transferred or traded.
Hyperliquid data inside Yutu
Yutu exposes Hyperliquid state to its execution layer. Applications can use market prices and order-book depth without relying on a single best price copied into a conventional oracle feed.
The swap pools use this access to walk the visible Hyperliquid ladder and calculate an executable price for a requested size. Other applications can use the same market connection for their own rules and settlement.
Public access
| Service | URL |
|---|---|
| JSON-RPC | https://rpc.yutu.finance |
| Explorer | explorer.yutu.finance |
| Bridge | bridge.yutu.finance |
EVM wallets and libraries connect through the standard Ethereum JSON-RPC API. The endpoint supports contract calls, gas estimation, transactions, receipts, blocks, balances, logs, filters, and subscriptions.
Read EVM on Yutu for the protocol precompiles and Write-precompile promises for contract-driven native orders.