Hyperliquid Docs
  • About Hyperliquid
    • Core contributors
  • Onboarding
    • How to start trading
    • How to use the HyperEVM
    • Connect mobile via QR code
    • Export your email wallet
    • Testnet faucet
  • HyperCore
    • Overview
    • Bridge
    • API servers
    • Clearinghouse
    • Oracle
    • Order book
    • Staking
    • Vaults
      • Protocol vaults
      • For vault leaders
      • For vault depositors
    • Multi-sig
  • HyperEVM
    • Tools for HyperEVM builders
  • Hyperliquid Improvement Proposals (HIPs)
    • HIP-1: Native token standard
    • HIP-2: Hyperliquidity
    • Frontend checks
  • Trading
    • Perpetual assets
    • Contract specifications
    • Fees
    • Builder codes
    • Order book
    • Order types
    • Take profit and stop loss orders (TP/SL)
    • Margining
    • Liquidations
    • Entry price and pnl
    • Funding
    • Miscellaneous UI
    • Auto-deleveraging
    • Robust price indices
    • Self-trade prevention
    • Portfolio graphs
    • Hyperps
    • Market making
  • Validators
    • Running a validator
    • Delegation program
  • Referrals
  • Points
  • Historical data
  • Risks
  • Bug bounty program
  • Audits
  • Brand kit
  • For developers
    • API
      • Notation
      • Asset IDs
      • Tick and lot size
      • Nonces and API wallets
      • Info endpoint
        • Perpetuals
        • Spot
      • Exchange endpoint
      • Websocket
        • Subscriptions
        • Post requests
        • Timeouts and heartbeats
      • Error responses
      • Rate limits
      • Bridge2
      • Deploying HIP-1 and HIP-2 assets
    • HyperEVM
      • Dual-block architecture
      • Raw HyperEVM block data
      • Interacting with HyperCore
      • HyperCore <> HyperEVM transfers
      • Wrapped HYPE
      • JSON-RPC
Powered by GitBook
On this page
  1. For developers
  2. HyperEVM

JSON-RPC

The following RPC endpoints are available

  • net_version

  • web3_clientVersion

  • eth_blockNumber

  • eth_call

    • only the latest block is supported

  • eth_chainId

  • eth_estimateGas

    • only the latest block is supported

  • eth_feeHistory

  • eth_gasPrice

    • returns the base fee for the next small block

  • eth_getBalance

    • only the latest block is supported

  • eth_getBlockByHash

  • eth_getBlockByNumber

  • eth_getBlockReceipts

  • eth_getBlockTransactionCountByHash

  • eth_getBlockTransactionCountByNumber

  • eth_getCode

    • only the latest block is supported

  • eth_getLogs

    • up to 4 topics

    • up to 50 blocks in query range

  • eth_getStorageAt

    • only the latest block is supported

  • eth_getTransactionByBlockHashAndIndex

  • eth_getTransactionByBlockNumberAndIndex

  • eth_getTransactionByHash

  • eth_getTransactionCount

    • only the latest block is supported

  • eth_getTransactionReceipt

  • eth_maxPriorityFeePerGas

    • always returns zero currently

  • eth_syncing

    • always returns false

The following custom endpoints are available

  • eth_bigBlockGasPrice

    • returns the base fee for the next big block

  • eth_getSystemTxsByBlockHash and eth_getSystemTxsByBlockNumber

    • similar to the "getTransaction" analogs but returns the system transactions that originate from HyperCore

Unsupported requests

  • Requests that require historical state are not supported at this time on the default RPC implementation. However, independent archive node implementations are available for use, and the GitHub repository has examples on how to get started indexing historical data locally.

PreviousWrapped HYPE

Last updated 15 days ago