You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{"jsonrpc":"2.0","id":1,"error":{"code":-32000,"message":"failed to get L2 output at block 0x1072048d5d3761e1649fa0e92a5cfa3a35ee9c737e047827b46871897b8d4420:18168390: failed to get contract proof at block 0x1072048d5d3761e1649fa0e92a5cfa3a35ee9c737e047827b46871897b8d4420: context deadline exceeded"}}
However, this works fine with an archive op-geth node.
Is there anything we can adjust or do to make this work with op-erigon?
// Careful! Because we must rewind the hash state
// and re-compute the state trie, the further back in time the request, the more
// computationally intensive the operation becomes.
// The current default has been chosen arbitrarily as 'useful' without likely being overly computationally intense.
So it's not recommened to use optimism_outputAtBlock for a past block with op-erigon now.
When querying op-node, attached to op-erigon, we get an error:
Query:
Response:
However, this works fine with an archive op-geth node.
Is there anything we can adjust or do to make this work with op-erigon?
Expected Response (taken from op-geth):
The text was updated successfully, but these errors were encountered: