Add an eth_getLogs-compatible endpoint that proxies into the indexer's log table. Many tools (TheGraph, Goldsky, Tenderly, indexing libraries) call eth_getLogs directly and expect block-range + topic-filter semantics.
Why
Sentrix's public RPC at rpc.sentrixchain.com runs against fullnodes that don't keep deep log history (CHAIN_WINDOW_SIZE rolls). Tools that need "all USDC transfers ever" hit a wall. The indexer has full log history in Postgres — exposing eth_getLogs over that fills the gap.
Scope
eth_getLogs JSON-RPC method served by the indexer (separate port or under /rpc)- Block-range support (
fromBlock / toBlock, including latest/earliest)
- Topic filter support (1, 2, 3, 4 topics with OR within position)
- Address filter (single or array)
- Pagination + max-result-cap (e.g. 10k logs per request) with continuation token
Acceptance
eth_getLogs returns identical results to running the same query on an archive node- Used by sentrix-dex subgraph for historical Swap event backfill
Add an
eth_getLogs-compatible endpoint that proxies into the indexer's log table. Many tools (TheGraph, Goldsky, Tenderly, indexing libraries) calleth_getLogsdirectly and expect block-range + topic-filter semantics.Why
Sentrix's public RPC at
rpc.sentrixchain.comruns against fullnodes that don't keep deep log history (CHAIN_WINDOW_SIZE rolls). Tools that need "all USDC transfers ever" hit a wall. The indexer has full log history in Postgres — exposing eth_getLogs over that fills the gap.Scope
eth_getLogsJSON-RPC method served by the indexer (separate port or under/rpc)fromBlock/toBlock, includinglatest/earliest)Acceptance
eth_getLogsreturns identical results to running the same query on an archive node