-
Notifications
You must be signed in to change notification settings - Fork 1.7k
VM trace bug(?). Ether disappeared from address. #7765
Comments
I confirm issue. Also found probably same problem for address: You can check balances here: https://etherscan.io/balancecheck-tool?a=0x4509008d923ef571fc1d29fd66d3135fa02f0b64 |
I confirm the other also:
|
Another address:
Whole block trace: There is no one trace what transfers to this address anything in the block 3852626. |
I have upgraded the client to |
I'm having the same issue, it looks like there is a missing transfer from I'm also missing ether in |
@iFA88 @alvarosevilla95 Did you guys re-import the chain while using 1.9.3? It is required to regenerate the trace database. |
Yes. Completely re synced. |
Looks like whatever is going on is indeed happening in transactions The
Neither of these changes can be explained by the trace, and same thing in
Here are the full traces and stateDiffs for both txs: |
Updated to 1.9.4 and resynced but no changes. |
Some more info on transaction According to etherscan the transaction calls the function
And the following events were emitted:
It looks like |
On |
It seems this issue is still reproduced for this address https://etherscan.io/address/0x4509008d923ef571fc1d29fd66d3135fa02f0b64. You can see it's marked with the tag "Bugs" and points to this issue. The other 4 addresses where this bug is reproduced are in the Limitations section in this article https://medium.com/google-cloud/how-to-query-balances-for-all-ethereum-addresses-in-bigquery-fb594e4034a7. Parity version 2.0.8. |
In which block do you have found a balance difference for 0x4509008d923eF571FC1D29fD66D3135Fa02f0B64 address? |
@iFA88 I assume it's block 4011777, as I see the difference of 1 Ether. As you detailed in your comment above:
Seems there is a missing trace moving 1 Ether to a precompiled contract at 0x0000000000000000000000000000000000000001 in this transaction 0x51c0baead6c3d9e5cb678fe534ef33e61627a321b4b8ee60a21b47acc432fa84. Is the issue still reproduced for you? |
I have upgraded my parity and resynced. The trace looks now:
For this TX the issue has been solved. I use now this: |
That's great! I'll try to resync my node with 2.0.9 and will report back. |
I run
Parity/v1.8.6-beta-2d051e4-20180109/x86_64-linux-gnu/rustc1.22.1
, but on Etherscan I got the same result.There is one transaction in the block nr 3852626 who calls this contract.
https://etherscan.io/tx/0x92ddeb8df37c1b43debeecb07aa25a0ed96f13f8405aca9dba08ab204a8d2e29
Here is the trace:
In the trace is only one ether transfer with 436224723746816 WEI (0x18cbe7bb38000).
Where is the other 21375011463593984 WEI from the address?
The text was updated successfully, but these errors were encountered: