Advanced
In reply to @scott
dcposch.eth@dcposch.eth
8/9/2023

Yes this is for my indexer The trouble is - Call eth_call with “latest” to get the current balance - Call eth_logs “latest” for logs No guarantee that they match! You might be missing a transfer needed to explain the balance.

In reply to @dcposch.eth
dcposch.eth@dcposch.eth
8/9/2023

So what if you fetch the latest block first , then pass that block number explicitly to eth_call and _getLogs? As far as I can tell , eth_logs will return successfully and still not guarantee that it actually has all logs thru that block. Wack

In reply to @dcposch.eth
Scott Sunarto@scott
8/9/2023

I would try using parity_subscribe. It's a more powerful version of eth_subscribe that basically allows you to subscribe to arbitrary eth_ rpc endpoint. so for your usecase, you can subscribe to both call and logs nethereum node supports them https://docs.nethereum.com/en/latest/nethereum-subscriptions-streaming/

In reply to @dcposch.eth
8/9/2023

i also keep running into issues where logs are missed, especially with new logs. my guess is that's from reorgs? only way that works for me is to do occasional resyncs and store everything in my own db to query from there.