fix: stop caching -32602 state-unavailable errors as deterministic#37
Merged
Conversation
Bump eth-go to develop tip which no longer classifies -32602 state-unavailable errors (pruned/historical state not found) as deterministic. Such errors depend on node pruning state and must not be persisted permanently in the executor call cache.
The eth-go bump transitively pulled x/crypto v0.44.0 which carries the November 2025 batch of critical SSH agent/crypto advisories (GHSA-vgwf-h737-ff37 and friends). Pin x/crypto to v0.45.0, the first patched release, which clears them without forcing a Go directive bump.
billettc
approved these changes
Jul 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
A caching proxy was persisting this error permanently in the executor call cache:
The error was classified as deterministic (
from_cache: true), but it must not be.-32602state-unavailable errors depend on the node's pruning state — an archive node, or the same node later, answers the call correctly. Caching it poisons the(block, to, data)key with a wrong permanent error.Root cause
eth-go'sIsGenericDeterministicErrorblanket-treated code-32602(JSON-RPC invalid argument) as deterministic, trusting the code alone. Some nodes reuse-32602for "block / historical state not found", a node-state condition rather than a property of the call.Fix
The real fix lives in
eth-go(message guard excluding state-unavailable messages from the generic deterministic heuristic). This PR bumpseth-goto thedeveloptip (2e53ff6) carrying that fix, so evmx no longer caches these errors.Verification
go build ./...cleango test ./executor/... ./json-rpc/...green