-
Notifications
You must be signed in to change notification settings - Fork 20k
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
Incorrect receipt for the tx 0x8b21c385f137ce75b3f2b0ee84040b629208d5037d0101d23c8bd2ce98e3a89b #29550
Comments
Tx: https://sepolia.etherscan.io/tx/0x8b21c385f137ce75b3f2b0ee84040b629208d5037d0101d23c8bd2ce98e3a89b Yep, confirm that this seems odd. I first thought it was a problem with the index during reorg, that we've recently fixed, but if so I would have expected the blockhash to mismatch. @rjl493456442 any thoughts? |
Probably the block with same transaction set but different order? |
Then the blockhash would mismatch. Unless I have misunderstood the bug |
Right, the transactionRoot will be different. |
Apparently the responded transaction hash is so, the (a) block number (b) block hash are all correct, but the transaction index is wrong. but the interesting thing is transaction index is not persisted in the txlookup(only the block number). Index is determined after loading the block body instead. body := ReadBody(db, blockHash, *blockNumber)
if body == nil {
log.Error("Transaction referenced missing", "number", *blockNumber, "hash", blockHash)
return nil, common.Hash{}, 0, 0
}
for txIndex, tx := range body.Transactions {
if tx.Hash() == hash {
return tx, blockHash, *blockNumber, uint64(txIndex)
}
} @AlbertMakhortov could you please restart your geth node and then retrieve the receipt? Just want to confirm it's relevant with a bug we have already fixed. |
@rjl493456442 we have restarted the node, and it helped |
@rjl493456442 Can you please point us to this bug/fix? |
Ethereum sepolia
System information
Geth version: v1.13.11
CL client & version: nimbus amd64-v24.2.0
OS & Version: linux
Expected behaviour
when requesting eth_getTransactionReceipt for 0x8b21c385f137ce75b3f2b0ee84040b629208d5037d0101d23c8bd2ce98e3a89b
expected transactionIndex is 0x26
Actual behaviour
transactionIndex in response is 0x14
full response:
We cannot reproduce this issue right now, because it was fixed by restarting the node, but the problem has arisen not for the first time, and we want to understand what is causing it
Backtrace
When submitting logs: please submit them as text and not screenshots.
The text was updated successfully, but these errors were encountered: