-
-
Notifications
You must be signed in to change notification settings - Fork 743
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
bug: Failing to find pending transactions #1540
Comments
Just had a forge-anvil test failing on this too. Was using alchemy rpc url btw. And I've seen it on wagmi react hook few times also. But it's inconsistent and a bit hard to reproduce. Perhaps issue is somewhere around that exponential backoff in |
Maybe we can increase the waiting time |
Interesting I wonder if this issue is from the RPC instead of viem? |
I was initially working with erigon, I've also tried nethermind but I do still see the same issue. It does seem to be an issue with timing though, ie. for those transactions that are not found if I immediately try to get the transaction with an rpc call via curl ( |
So it's an RPC issue then. Might be worth performing some polling to get the example in OP to work. |
This issue has been locked since it has been closed for more than 14 days. If you found a concrete bug or regression related to it, please open a new bug report with a reproduction against the latest Viem version. If you have any questions or comments you can create a new discussion thread. |
Is there an existing issue for this?
Package Version
1.19.9
Current Behavior
When looking at pending transactions in the mempool, a
Transaction with hash <hash> could not be found.
error gets thrown often. I am currently polling using an http transport and I am using a local Erigon archive node. This is a similar issue to #161, but in my case, the transactions that can't be found are recentI also verify that the transactions are new by checking etherscan
Expected Behavior
I expect that every transaction hash that comes in should be ready to be queried on the node
Steps To Reproduce
This outputs the following
Checking against my node, transactions which are reported to not be found can in fact be found
cast receipt 0x29ff06972fb4fb696227cc2a61b3a00c6ab79a85444e8a91aa49adcf2b461381 blockHash 0x7d85773948df1e5470f1d2fee88be13e10c809ad1fbbe0bf72eb8a1c3193ffbf blockNumber 18666359 contractAddress cumulativeGasUsed 9905815 effectiveGasPrice 30395534762 gasUsed 21000 logs [] logsBloom 0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 root status 1 transactionHash 0x29ff06972fb4fb696227cc2a61b3a00c6ab79a85444e8a91aa49adcf2b461381 transactionIndex 70 type 1
Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: