For the complete documentation index, see llms.txt. This page is also available as Markdown.

eth_getLogs

eth_getLogs JSON-RPC reference for MegaETH.

Summary

Returns event logs emitted by smart contracts, filtered by block range, contract address, and/or topics.

The public MegaETH endpoint supports this method. The standard, node, and gateway layers below identify behavior that differs from a generic Ethereum endpoint.

Parameters

filter object REQUIRED

Log filter.

  • fromBlock string

    Inclusive start as a hex block number or tag. The default is latest.

  • toBlock string

    Inclusive end as a hex block number or tag. The default is latest.

  • blockHash Hash32

    Single-block mode; mutually exclusive with fromBlock/toBlock.

  • address Address | Address[]

    Filter by emitting address(es).

  • topics array

    Positional topic filter where positions are AND and values within a position are OR. Use null for wildcards.

Result

Log[] — array of matching log entries.

  • address Address

    Emitting contract.

  • topics Hash32[]

    Indexed topics.

  • data Data

    Unindexed payload.

  • blockNumber Quantity | null

    Containing block number.

  • transactionHash Hash32 | null

    Containing transaction hash.

  • transactionIndex Quantity | null

    Transaction position in block.

  • logIndex Quantity | null

    Log position in block.

  • removed boolean

    true if removed during reorg.

  • blockTimestamp Quantity

    Block timestamp.

Comparison with Ethereum Standard JSON-RPC

Ethereum Standard

The canonical Ethereum method uses the parameter and result contract documented above, including the stated null, false, or zero-value semantics where applicable.

MegaETH Node Behavior

The node applies the standard address/topic filter and enforces canonical block-selector encoding. Backend retention can still affect historical ranges.

MegaETH Public Gateway

The gateway places the method in the IO-heavy tier, routes older explicit ranges to its ClickHouse-backed log service when configured, streams the response, and caches only cache-safe filters. There is no gateway block-range cap, but backend row, time, or memory limits can still make very large queries incomplete or fail.

Errors

The | Scope | column distinguishes method failures from gateway policy errors.

Code
Scope
Message
When it happens

-32602

Request

Invalid params

Filter is malformed or combines blockHash with fromBlock/toBlock

-32001

Method

Resource not found

Provided blockHash cannot be resolved

-32000

Method

Server error

Query range is too large for the endpoint

-32005

Transport/policy

Rate limit exceeded

The caller exceeds the public gateway's IO-heavy read budget.

-32099

Transport/policy

Payload too large

The request body exceeds the 128 KiB public endpoint limit.

See also Error Codes.

Examples

Endpoint: https://mainnet.megaeth.com/rpc

Capture date: July 24, 2026

Outcome: success

Sources

  • Spec: [email protected]:ethereum/execution-apis.git @ d24f58b56dcd16ab0f0c70ec609bcc1c42750b51: src/eth/filter.yaml

  • Code: [email protected]:megaeth-labs/mega-reth.git @ ab60376631228edab3a6df180f295280bad26e93: crates/rpc/rpc-eth-api/src/filter.rs

  • Code: [email protected]:megaeth-labs/mega-rpc.git @ 06aa35aa95d569c227cc25d2aa12834eb0458aa0: workers/src/processors/eth-logs-processor.ts

  • Probe: MegaETH Mainnet public endpoint, July 24, 2026

Last updated