Skip to content
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

stateDiff in trace shows zero entry #8610

Closed
1 task done
mcdee opened this issue Jun 5, 2024 · 0 comments · Fixed by paradigmxyz/revm-inspectors#139
Closed
1 task done

stateDiff in trace shows zero entry #8610

mcdee opened this issue Jun 5, 2024 · 0 comments · Fixed by paradigmxyz/revm-inspectors#139
Assignees
Labels
A-rpc Related to the RPC implementation C-bug An unexpected or incorrect behavior

Comments

@mcdee
Copy link

mcdee commented Jun 5, 2024

Describe the bug

Running trace_replayBlockTransactions on blocks I regularly see what looks like a zero entry in the state diff. For example, for transaction 0x19dc9c21232699a274849fac7443be6de819755a07b7175a21d337e223070709 on sepolia I see the following

    {
      "output": "0x",
      "stateDiff": {
        "0x15dd773dad3f630773a0e771e9b221f4c8b9b939": {
          "balance": {
            "+": "0x0"
          },
          "code": {
            "+": "0x"
          },
          "nonce": {
            "+": "0x0"
          },
          "storage": {}
        },
        "0x283b5b7d75e3e6b84b8e2161e8a468d733bbbe8d": {
          "balance": {
            "*": {
              "from": "0x328c0afdca728e08",
              "to": "0x328a1eb94ad20578"
            }
          },
          "code": "=",
          "nonce": {
            "*": {
              "from": "0xb96",
              "to": "0xb97"
            }
          },
          "storage": {}
        },
        "0xe276bc378a527a8792b353cdca5b5e53263dfb9e": {
          "balance": {
            "*": {
              "from": "0x5274355d48bb55f1e11a1c",
              "to": "0x5274355d48ce6f636b6a1c"
            }
          },
          "code": "=",
          "nonce": "=",
          "storage": {}
        }
      },
      "trace": [],
      "transactionHash": "0x19dc9c21232699a274849fac7443be6de819755a07b7175a21d337e223070709",
      "vmTrace": null
    },

The entry for 0x15dd773dad3f630773a0e771e9b221f4c8b9b939 shows no information, and from what I can see this address has never held a balance or storage. As such ,this entry appears to be erroneous. Checking on other nodes (besu, erigon) this entry does not show up.

Steps to reproduce

Run curl -s -H 'Content-type: application/json' --data '{"jsonrpc":"2.0","method":"trace_replayTransaction","params":["0x19dc9c21232699a274849fac7443be6de819755a07b7175a21d337e223070709",["stateDiff"]],"id":67}' http://localhost:8545 against a suitable reth node to see the output.

Node logs

No response

Platform(s)

Linux (x86)

What version/commit are you on?

reth Version: 0.2.0-beta.8
Commit SHA: c0e7440
Build Timestamp: 2024-06-03T18:16:52.375796153Z
Build Features: jemalloc
Build Profile: maxperf

What database version are you on?

Current database version: 2
Local database version: 2

Which chain / network are you on?

sepolia

What type of node are you running?

Archive (default)

What prune config do you use, if any?

No response

If you've built Reth from source, provide the full command you used

No response

Code of Conduct

  • I agree to follow the Code of Conduct
@mcdee mcdee added C-bug An unexpected or incorrect behavior S-needs-triage This issue needs to be labelled labels Jun 5, 2024
@mattsse mattsse self-assigned this Jun 5, 2024
@mattsse mattsse added A-rpc Related to the RPC implementation and removed S-needs-triage This issue needs to be labelled labels Jun 5, 2024
mattsse added a commit to paradigmxyz/revm-inspectors that referenced this issue Jun 6, 2024
closes paradigmxyz/reth#8610

LoadedAsNonExisting is the default, we should not treat them as created
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-rpc Related to the RPC implementation C-bug An unexpected or incorrect behavior
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants