Skip to content

Conversation

@nick1udwig
Copy link
Member

@nick1udwig nick1udwig commented Sep 4, 2025

Problem

  1. ETH runtime module is brittle to RPC failure
  2. hypermap-cacher is too closely built around Alchemy API settings (which just changed!)

Solution

  1. Improve ETH runtime module by making RPC entries definitely ordered and by tracking what methods an RPC has failed to serve (and skipping that RPC for those methods in future; and retrying on RPC failures to allow for un-marking of failure if it is intermittent)
  2. Reduce that. Instead we now try to getLogs for the entire history of logs and halve the log range until it works

Testing

  • Getting logs from scratch without any hypermap-cacher bootstrapping nodes
  • Falling back from one RPC to another
  • Proper setting of log range for range-limited RPC providers

Docs Update

None

Notes

Future work on/around ETH runtime module:

  1. Script(s) to change ordering of ETH RPCs

@dolled-possum

@nick1udwig nick1udwig force-pushed the hf/eth-handle-unresponsive-rpcs branch from 9a2024a to 3e3e1a6 Compare September 4, 2025 22:01
@nick1udwig nick1udwig marked this pull request as ready for review September 5, 2025 00:07
@nick1udwig nick1udwig merged commit 4215a88 into develop Sep 5, 2025
1 check passed
@nick1udwig nick1udwig deleted the hf/eth-handle-unresponsive-rpcs branch September 5, 2025 00:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants