eth_getLogs on Story
Measured 2026-10-11 by our weekly probe, which calls eth_getLogs through the same Story 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 Story: what we measured
- Measured block-range cap: 50,000 blocks per call, about 32.8 hours of Story at 2.4 s blocks. Wider ranges are rejected; page through history in windows below the cap and filter by address where you can.
- The finalized tag tracks the head on Story (instant finality), so results at "latest" do not get reorganised.
Example request
curl -s https://rpc.swiftnodes.io/rpc/story?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/story?key=YOUR_API_KEY") });
// Any JSON-RPC method, typed loosely: eth_getLogs on Story
const result = await client.request({
method: "eth_getLogs",
params: [{"fromBlock":"latest","toBlock":"latest"}],
});Other methods on Story
- eth_blockNumberSupported
- eth_chainIdSupported
- eth_getBalanceSupported
- eth_getBlockByNumberSupported
- eth_getTransactionByHashNot measured
- eth_getTransactionReceiptNot measured
- eth_callSupported
- eth_estimateGasSupported
- eth_gasPriceSupported
- eth_maxPriorityFeePerGasSupported
- eth_sendRawTransactionSupported
- eth_getTransactionCountNot measured
- eth_getCodeSupported
- eth_subscribeSupported
- eth_getBlockReceiptsSupported
- eth_feeHistorySupported
- eth_getProofSupported
- eth_createAccessListSupported
- debug_traceCallNot available
- trace_blockNot available
- trace_transactionNot available
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
- Lisk
- Hemi
- X Layer
- BOB
- Plasma
- Fraxtal
- Zora
- Soneium
- Sei
- Hyperliquid
- Taiko
- Morph
- Ink
- Katana
- Ethereum Classic
- opBNB
- Mode
- Flare
- Core
- Chiliz
- Telos EVM
- Tempo
- Cronos
- Manta Pacific
- Shibarium
- Boba Network
- Arbitrum Nova
- Immutable zkEVM
Frequently asked questions
Does Story support eth_getLogs?
Yes. eth_getLogs answered correctly on the SwiftNodes Story endpoint in our weekly method probe (2026-10-11), which sends real requests through the customer path.
Are there limits on eth_getLogs on Story?
Measured block-range cap: 50,000 blocks per call, about 32.8 hours of Story at 2.4 s blocks. Wider ranges are rejected; page through history in windows below the cap and filter by address where you can.
Story endpoints, live block height and WebSocket status are on the Story RPC page.
One key covers every chain we serve, and SwiftNodes has a free tier.