RPC method

eth_getLogs on Fantom

Supported on SwiftNodes

Measured 2026-10-04 by our weekly probe, which calls eth_getLogs through the same Fantom 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 Fantom: what we measured

  • Fantom does not expose the finalized block tag on our upstreams, so treat recent results as provisional and re-check after a reorg window.

Example request

curl -s https://rpc.swiftnodes.io/rpc/fantom?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/fantom?key=YOUR_API_KEY") });

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

Other methods on Fantom

eth_getLogs on other chains

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

Frequently asked questions

Does Fantom support eth_getLogs?

Yes. eth_getLogs answered correctly on the SwiftNodes Fantom endpoint in our weekly method probe (2026-10-04), which sends real requests through the customer path.

Are there limits on eth_getLogs on Fantom?

Fantom does not expose the finalized block tag on our upstreams, so treat recent results as provisional and re-check after a reorg window.

Fantom endpoints, live block height and WebSocket status are on the Fantom RPC page.

One key covers every chain we serve, and SwiftNodes has a free tier.