-
Notifications
You must be signed in to change notification settings - Fork 20.2k
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
From address for some transactions is 0x0 address (0x0000000000000000000000000000000000000000) #23681
Labels
Comments
kurushdubash
changed the title
From address for some transactions is 0x address (Transactions are returning with from address as burn address (0x0000000000000000000000000000000000000000)
From address for some transactions is 0x address (0x0000000000000000000000000000000000000000)
Oct 4, 2021
kurushdubash
changed the title
From address for some transactions is 0x address (0x0000000000000000000000000000000000000000)
From address for some transactions is 0x0 address (0x0000000000000000000000000000000000000000)
Oct 4, 2021
The issue is we default to the go-ethereum/internal/ethapi/api.go Line 1297 in 307156c
|
fjl
pushed a commit
that referenced
this issue
Oct 7, 2021
Fixes #23681 After the fix I get the address 0x6d6d02e83c4ced98204e20126acf27e9d87b8af2 for the tx mentioned in the ticket, which agrees with etherscan.
sidhujag
pushed a commit
to syscoin/go-ethereum
that referenced
this issue
Oct 7, 2021
…#23683) Fixes ethereum#23681 After the fix I get the address 0x6d6d02e83c4ced98204e20126acf27e9d87b8af2 for the tx mentioned in the ticket, which agrees with etherscan.
yongjun925
pushed a commit
to DODOEX/go-ethereum
that referenced
this issue
Dec 3, 2022
…#23683) Fixes ethereum#23681 After the fix I get the address 0x6d6d02e83c4ced98204e20126acf27e9d87b8af2 for the tx mentioned in the ticket, which agrees with etherscan.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System information
Geth version:
geth-v1.10.8
OS & Version: Linux - 32GiB Mem (~11 GiB used), Disk: 10TB (8.4TB used)
Expected behaviour
When fetching a block with full transaction payloads, we are noticing transactions with
from
address coming from the Eth burn address (0x0000000000000000000000000000000000000000
) which should never be possible.As an example, for block
0x24e19
(151065)We'd expect the response:
but
Actual response
Noticeable, the
from
address of the only transaction is invalid.Steps to reproduce the behaviour
Call
getBlockByNumber
with concerning blocks with full transactions. Likewise, callinggetTransactionByHash
with the appropriate transaction hash will also output same issue with the transaction where thefrom
field is0x0000000000000000000000000000000000000000
.We've noticed this on multiple blocks ranging from
81914
to207680
and potentially more. Our hunch is that there is some issue with the RLP decoder that is defaulting thefrom
field to the0x0
address after a Geth upgrade.All transactions of issue that we've noticed are contained in blocks prior to the
Homestead
fork so far.The text was updated successfully, but these errors were encountered: