A place for developers to talk about building on Farcaster.

/dev

Ponder

After years of "web3" development, I still can't get over how arbitrarily stupid RPC nodes limitations are. Take eth_getLogs: Alchemy offers 100k, QuickNode — 10k, but these numbers can be different depending on how many results will be returned.

You either have to code against a single RPC provider (lock in) or run something like /ponder or graph (ops complexity++)

FWIW here's our solution from the `@ponder/utils` package (open-source but poorly documented rn). It handles ~20 different eth_getLogs implementations.

Your critique is spot-on, though - the standard RPC is underspecified!

FWIW here's our solution from the `@ponder/utils` package (open-source but poorly documented rn). It handles ~20 different eth_getLogs implementations.

Your critique is spot-on, though - the standard RPC is underspecified!

https://github.com/ponder-sh/ponder/blob/main/packages/utils/src/getLogsRetryHelper.ts#L36

Building ponder.sh. EVM, TypeScript, open-source enjoyer.

We're planning to publish a Viem transport sometime soon that incorporates everything we've learned about RPC providers from the client perspective.

Goal is to be able to throw a list of RPC URLs into and it will handle eth_getLogs range retries, smart load balancing, fallback, etc.

Oh main reading this file triggers PTSD from dealing with all these things ad-hoc through dozen of projects lol