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
Is your feature request related to a problem? Please describe.
While operating a full archive node, transactions older than 2.3M blocks will no longer be returned by getTransactionByHash
Per discussion on Discord, this is expected:
me: "Is it right that a receipt being purged should cause getTransactionByHash to deny the existence of the tx? It can still be observed by fetching the block it’s contained in"
Ashraf: "it just does not save all of the txhash -> block mapping which take up a lof of space"). Full archive nodes already, self-evidently, don't care about space.
This was encountered while launching Gnosis Safe onto our chain, it simply would not index what I thought was a full archive node.
Describe the solution you'd like
Default the TxLookupLimit to 0 when Pruning is None.
Is your feature request related to a problem? Please describe.
While operating a full archive node, transactions older than 2.3M blocks will no longer be returned by getTransactionByHash
Per discussion on Discord, this is expected:
This was encountered while launching Gnosis Safe onto our chain, it simply would not index what I thought was a full archive node.
Describe the solution you'd like
Default the TxLookupLimit to 0 when Pruning is None.
Describe alternatives you've considered
I've asked safe-global to mention this specific requirement on https://docs.safe.global/advanced/api-rpc-requirements .
The text was updated successfully, but these errors were encountered: