eth_getLogs — Robinhood Chain JSON-RPC
Return event logs matching a filter.
https://triport.io/rpc/robinhood- Network
- Robinhood Chain mainnet (chain ID 4663)
- Scope
- robinhood:rpc
- Auth
- x-token: $TRIPORT_API_KEY
- Rate limit
- robinhood_read_rpc_heavy - 15 / 20 / 100 / 250 RPS sustained · short burst 30 / 40 / 200 / 500 (free / basic / pro / business) (plan policy); enterprise unlimited; Burst capacity
Endpoint and plans: Robinhood Chain RPC endpoint.
eth_getLogs — return event logs matching a filter. The published signature and response shape come from the measured Robinhood OpenRPC contract (chain ID 4663).
Historical events by range and filter: the backbone of transfer monitoring and indexing. Always bound the range and filter by address or topics. The range ceiling is not one number here — it is limited differently on every channel — and deep ranges may be split or reconstructed from block receipts, which is the slower path.
Parameters
JSON-RPC params is a positional array.
filterLogFilterrequiredfromBlock/toBlock (or blockHash), address (string or array) and positional topics. Bound the range — ceilings depend on the serving channel.Response
A measured response from Robinhood Chain mainnet.
Errors
See Robinhood errors. Invalid parameters return a JSON-RPC parameter error; authentication and rate-limit failures use the shared client error contract. Unknown failures are returned without an implicit retry.
Examples
const response = await fetch("https://triport.io/rpc/robinhood", {
method: "POST",
headers: { "x-token": process.env.TRIPORT_API_KEY, "Content-Type": "application/json" },
body: JSON.stringify({"jsonrpc":"2.0","id":1,"method":"eth_getLogs","params":[{"fromBlock":"0x3626dfe","toBlock":"0x3626e62","address":"0x8366a39cc670b4001a1121b8f6a443a643e40951","topics":["0x40e9cecb9f5f1f1c5b9c97dec2917b7ee92e57ba5563708daca94dd84ad7112f"]}]}),
});
const payload = await response.json();Notes
- Every upstream channel has a different measured range/result ceiling. Triport may reconstruct deep ranges from block receipts; that path is slower.
- Always bound the range and use
addressortopicswhere possible. - The block range in the example above is the one the response below it was measured at, so request and response match. It is historical: a range that no serving channel can answer fails with an error (
-32000"log data unavailable") instead of an empty list, so point a live call at a recent window and see archive for the measured floor.