Skip to main content

Build on Yutu

Yutu applications can use EVM contracts, protocol precompiles, and Hyperliquid market data from the same network.

The public JSON-RPC endpoint is:

https://rpc.yutu.finance

Ethereum JSON-RPC​

Standard EVM wallets and libraries can connect to Yutu. Contracts pay gas in HYPE and appear in the Yutu explorer with their transactions, receipts, code, balances, and logs.

The endpoint supports the Ethereum methods used by wallets, contract tooling, explorers, and indexers, including:

  • Chain and node state through eth_chainId, eth_blockNumber, eth_syncing, net_version, and web3_clientVersion
  • Contract reads through eth_call, eth_getCode, eth_getStorageAt, and eth_getBalance
  • Gas pricing through eth_estimateGas, eth_gasPrice, eth_maxPriorityFeePerGas, and eth_feeHistory
  • Transactions and receipts through eth_sendRawTransaction, eth_getTransactionByHash, and eth_getTransactionReceipt
  • Blocks and logs through eth_getBlockByNumber, eth_getBlockByHash, eth_getBlockReceipts, and eth_getLogs
  • Filters and WebSocket subscriptions for new heads and matching logs. Pending-transaction subscriptions are accepted but remain silent because transactions commit immediately.

Use the EVM path for contract state, token transfers, swap integrations, and application settlement.

Yutu's write precompile also lets a contract submit an order to the native market engine. It returns a promise ticket that can be polled or resolved through a chain callback. Read Write-precompile promises for the execution model.

Hyperliquid market data​

The Yutu execution layer can read Hyperliquid price and depth data. Contracts can use that connection to price size-aware trades or apply rules based on the visible market.

Yutu's swap pools are one implementation: they walk Hyperliquid's price levels, calculate a volume-weighted average price, and bound the trade by available depth.

Builder fees​

Applications integrating supported swaps can add a fee to the quote. The router enforces the rate and sends the full third-party fee to the builder address.

Read Builder fees for the payment rules and user bounds.