-
Notifications
You must be signed in to change notification settings - Fork 20.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
web3.eth.getTransaction returns null for existing, older than a year transactions in mainnet #22661
Comments
@lukerQuant is this the same issue you reported yesterday here #22644 (comment) ? |
https://github.com/ethereum/go-ethereum/releases/tag/v1.10.0
|
Yes it was. For me it was difficult to find this information but hopefully from now on developers will have the notes placed here to point them in the correct direction 👍 |
@holiman Thank You!!! But I don't understand how this is supposed to work. My node is in sync, I put the @lukerQuant unfortunately the same happened to me! |
Yes, you should see something along the lines of |
I'm running a geth node in mainnet, version Kepler Verge (v1.10.2). The sync mode is "fast".
When I try to execute web3.eth.getTransaction for some old transaction (e.g. 0x74e51fb791fe430856ca0d55fdfd63d8ba08463a725241a6bc9c031f6c221874) I get null. The same happens with web3.eth.getTransactionReceipt.
What's wrong here? Shouldn't a fast node be capable of handling at least getTransaction?
If I do the same test with a more recent transaction (e.g. 0x53ea196d87a8cdd05a02abd41d80a99b7f0e1814824819cb2fd8f4b05e3a44a7) I'm able to get everything right.
The node has been created and synced less than a week ago. What's going on here?
The text was updated successfully, but these errors were encountered: