Open svanegmond opened 6 months ago
the documentation page I'm talking about is here - https://docs.safe.global/advanced/api-rpc-requirements
Ok. My point of pointing all this out is that if you start a Safe instance and begin using Safe, it will work. If you start to commission a Safe instance a few million blocks after beginning to use Safe, it will forever be stuck (with few useful log outputs) trying to obtain transactions it can never obtain.
For ongoing operations, sure, turn off full archive, but it needs to be on for initial scan to succeed.
This appears to be chatGPT.
I know what the problem is.
This bug is giving suggestions to improve the documentation.
Feel free to send a PR to safe-docs
Describe the bug
Nethermind requires additional settings to work with Safe beyond the requirement for an archive node.
To Reproduce
The issue is the setting Receipt.TxLookupLimit. It is documented like this:
I confirmed on the Nethermind discord:
Nethermind dev replied:
I have filed a feature request to cause the TxLookupLimit to be 0 when pruning is disabled. We'll see if they agree. Meantime, can you document that Receipt.TxLookupLimit must be set to 0 in order to be able to index "old" transactions?