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
  • Hyperliquid L1
    • L1 overview
    • Staking
    • HyperEVM
    • Bridge
    • API servers
    • Clearinghouse
    • Oracle
    • Order book
    • Multi-sig
  • 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
    • Uniswap perpetuals
    • Hyperps
    • Market making
  • Vaults
    • Protocol vaults
    • For vault leaders
    • For vault depositors
  • 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

Raw HyperEVM block data

PreviousDual-block architectureNextInteracting with HyperCore

Last updated 1 month ago

Builders that wish to index the HyperEVM without running a node can use the S3 bucket: aws s3 ls s3://hl-mainnet-evm-blocks/ --request-payer requester .

There is a similar bucket s3://hl-testnet-evm-blocks/ for testnet.

Some potential applications include a JSON-RPC server with custom rate limits, a HyperEVM block explorer, or other indexed services and tooling for builders.

While the data is public for anyone to use, the requester must pay for data transfer costs. The filenames are predictably indexed by EVM block number, e.g. s3://hl-mainnet-evm-blocks/0/6000/6123.rmp.lz4. An indexer can copy block data from S3 on new HyperEVM blocks. The files are stored in MessagePack format and then compressed using LZ4.

Note that testnet starts with directory s3://hl-testnet-evm-blocks/18000000and the earlier testnet RPC blocks were not backfilled.

An example can be found in the Python SDK:

https://github.com/hyperliquid-dex/hyperliquid-python-sdk/blob/master/examples/evm_block_indexer.py