Content pfp
Content
@
0 reply
0 recast
2 reactions

W1NTΞR pfp
W1NTΞR
@w1nt3r
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++)
7 replies
0 recast
61 reactions

Kevin pfp
Kevin
@typedarray.eth
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
2 replies
0 recast
1 reaction

W1NTΞR pfp
W1NTΞR
@w1nt3r
Oh main reading this file triggers PTSD from dealing with all these things ad-hoc through dozen of projects lol
0 reply
0 recast
1 reaction