Indexing

One process runs one poll loop per chain. Each loop reads the chain head, stores any large transfers it finds, updates the status, then waits. This page describes the loops as they are coded, including what they miss.

#Poll intervals

The wait starts after a poll finishes, so the real cycle is the wait plus the time the RPC calls take. After a failed poll, the wait doubles, up to 60 seconds.

#The EVM poller

1. Send a batch of eth_getBlockByNumber("latest") and eth_gasPrice. On Ethereum, the block includes full transactions.
2. Update head, block time, lag, transaction count, gas ratio and fees. Add the block to the in-memory list of 25.
3. Stop here on OP Mainnet and Polygon.
4. On Ethereum, scan the head block's transactions. Store each one whose value times the ETH price is at least $100,000. Skip contract creations.
5. Call eth_getLogs for ERC-20 Transfer events of the curated tokens, from the block after the last scanned block, up to 200 blocks per poll.
6. For each log, compute amount and usd. Store it if usd is at least $100,000.
7. Move the cursor to the head.

Storage uses a unique uid. A row found twice is stored once, and it reaches rules and the stream once.

#The log scan cursor

The log range starts at the larger of cursor + 1 and head - 2000. It ends at the smaller of head and from + 199. The cursor then moves to the end of the range. A poll reads 200 blocks at most, which keeps each call small enough for public RPC limits. A chain that produces more blocks than that in one poll is caught up over later polls. No block is skipped unless the reader falls more than 2,000 blocks behind. scan_lag_blocks in Status shows the distance. The cursor is held in memory, so a restart begins again at the head.

This table was measured on 2026-11-04 UTC from the last 25 entries of Recent blocks. The log scan was changed after this measurement. All four chains fit inside the 200 block limit.

#The Solana poller

1. Send a batch of getSlot with finalized commitment, getRecentPerformanceSamples and getRecentPrioritizationFees.
2. Update TPS and the 75th percentile priority fee.
3. Call getBlock for that slot. If the RPC returns an error for it, try up to three older slots.
4. For each successful transaction in that one block, compute balance changes per owner for the curated Solana tokens, and per account for SOL.
5. For each asset, take the largest decrease and the largest increase. amount is the smaller of the two. Store it if usd is at least $100,000.

Only one block per poll is read. A separate loop reads recent transactions of 7 public exchange wallets every 120 s with the same logic. Read sampling before you use these rows.

#What gets missed

The Ethereum native scan checks the receipt of each transaction at or above the threshold. A reverted transaction is not stored. If the receipt read fails, the row is not stored either.

ERC-20 rows come from logs, and logs exist only for successful transactions.

#Other timers

#How to use this data

• Treat the index as a filter of large movements in a short list of tokens. It is not a full copy of any chain.
• Use sampled, chain and this page's table when you compute totals.
• Read indexed_since_start and last_ok from Status to tell whether a quiet period means a quiet chain or a stalled poller.