Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Misleading storage from trace_replayTransactions upon executing suicide on contract #8937
Before filing a new issue, please provide the following information.
Misleading storage from
Suppose a contract has 2 positions [
But, the response from
Let us take an example on the mainnet.
Transaction_hash 0x12945faff5df252934cfbc25353dbecf2175b5017a3990bb764b44b7cc763547 creates a contract
3 positions in the contract storage have some value associated to them. The next transaction 0xc4af9cd2bba88af9f0f8e8fdbda2537751ef55b7ecacab5b8f2dade34d69f691 suicides the contract. Again, the following is the contract relevant response to the method
Notice, the values in balance, code and nonce have been removed, but the 3 positions that had been initialized have not been removed after the suicide call.
Note: There are no values in the contract storage, when verified after exporting the state. Thus the storage values are being deleted.
Still get the same misleading result.
#8297 deals with adding account information to