eth_getLogs on Lisk

Measured 2026-10-04 by our weekly probe, which calls eth_getLogs through the same Lisk endpoint customers use.

What eth_getLogs does

Returns the event logs that match a filter: a block range, optional contract addresses and up to four topics. It is how indexers, dashboards and wallets read transfers, swaps and other contract events.

eth_getLogs on Lisk: what we measured

• Measured block-range cap: 50,000 blocks per call, about 27.8 hours of Lisk at 2.0 s blocks. Wider ranges are rejected; page through history in windows below the cap and filter by address where you can.
• The finalized tag trails the head by about 8,606 blocks (4.8 hours). Results newer than that can still change in a reorg; query up to "finalized" if you need settled data.

Example request

curl -s https://rpc.swiftnodes.io/rpc/lisk?key=YOUR_API_KEY \
  -X POST -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_getLogs","params":[{"fromBlock":"latest","toBlock":"latest"}]}'

import { createPublicClient, http } from "viem";

const client = createPublicClient({ transport: http("https://rpc.swiftnodes.io/rpc/lisk?key=YOUR_API_KEY") });

// Any JSON-RPC method, typed loosely: eth_getLogs on Lisk
const result = await client.request({
  method: "eth_getLogs",
  params: [{"fromBlock":"latest","toBlock":"latest"}],
});

Other methods on Lisk

• eth_getBlockReceiptsSupported
• eth_feeHistorySupported
• eth_getProofSupported
• eth_createAccessListSupported
• debug_traceCallSupported
• trace_blockSupported
• trace_transactionSupported

eth_getLogs on other chains

Support differs by chain; the full measured table is on the eth_getLogs reference.

• Ethereum
• Base
• Arbitrum
• Optimism
• Polygon
• BNB Smart Chain
• Avalanche
• Sonic
• Linea
• Scroll
• zkSync Era
• Blast
• Mantle
• Gnosis
• Celo
• Berachain
• Monad
• Unichain
• Kaia
• PulseChain
• World Chain
• Ronin
• Abstract
• ApeChain
• MegaETH
• Fantom
• Hemi
• X Layer
• BOB

Frequently asked questions