RPC method

eth_getLogs on Flare

Supported on SwiftNodes

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

  • The finalized tag tracks the head on Flare (instant finality), so results at "latest" do not get reorganised.

Example request

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

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

Other methods on Flare

eth_getLogs on other chains

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

Frequently asked questions

Does Flare support eth_getLogs?

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

Are there limits on eth_getLogs on Flare?

The finalized tag tracks the head on Flare (instant finality), so results at "latest" do not get reorganised.

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

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