Replies: 2 comments 1 reply
-
I would guess this has more to do with Geth than with ethers... |
Beta Was this translation helpful? Give feedback.
1 reply
-
I'm going to move it to discussions, but if someone finds it is a problem with ethers, please let me know. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
(sorry for the long title ;-))
Few days ago I upgraded my geth node from version 1.10.9 to 1.10.10 (the latest).
I noticed that when I get a transaction using
webserviceProviderManager.provider.getTransaction()
the returned from field is filled with0x0000000000000000000000000000000000000000
until the transaction is included in a block. I tried to pick a random (pending) example to show the difference while the transaction is in pending state versus when the transaction mined.This is before the tx is placed in block:
And this is what it looks when it is mined:
I was not getting this behaviour when my geth node was at the previous version. The issue might very well be with geth as that is the only thing changed in my setup, but that is hard for me to check..
Beta Was this translation helpful? Give feedback.
All reactions