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

eth_simulateV1 gives Transaction conversion error when it shouldn't #13421

Closed
1 task done
jonathanudd opened this issue Dec 17, 2024 · 2 comments
Closed
1 task done
Labels
C-bug An unexpected or incorrect behavior S-needs-triage This issue needs to be labelled S-stale This issue/PR is stale and will close with no further activity

Comments

@jonathanudd
Copy link

Describe the bug

I'm running a Base mainnet archive node using op-reth version 1.1.4.

This RPC request returns Transaction conversion error from our op-reth node but it works on a Base node running with op-geth

{
  "method": "eth_simulateV1",
  "jsonrpc": "2.0",
  "id": 1,
  "params": [
    {
      "blockStateCalls": [
        {
          "calls": [
            {
              "type": "0x2",
              "from": "0xd8da6bf26964af9d7eed9e03e53415d37aa96045",
              "nonce": "0x0",
              "maxFeePerGas": "0x1",
              "maxPriorityFeePerGas": "0x1",
              "gas": "0x5208",
              "to": "0xda9dfa130df4de4673b89022ee50ff26f6ea73cf",
              "value": "0xa",
              "input": "0x"
            }
          ],
          "stateOverrides": {}
        },
        {
          "calls": [
            {
              "type": "0x2",
              "from": "0xdeadbeefdeadbeefdeadbeefdeadbeefdeadbeef",
              "nonce": "0x0",
              "maxPriorityFeePerGas": "0x0",
              "gas": "0x1c9c380",
              "to": "0xca11bde05977b3631167028862be2a173976ca11",
              "value": "0x0",
              "input": "0x82ad56cb0000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000100000000000000000000000000ca11bde05977b3631167028862be2a173976ca110000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000244d2301cc000000000000000000000000d8da6bf26964af9d7eed9e03e53415d37aa9604500000000000000000000000000000000000000000000000000000000000000000000000000000000ca11bde05977b3631167028862be2a173976ca110000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000244d2301cc000000000000000000000000da9dfa130df4de4673b89022ee50ff26f6ea73cf00000000000000000000000000000000000000000000000000000000"
            }
          ]
        }
      ],
      "traceTransfers": true,
      "validation": false
    },
    "latest"
  ]
}

Steps to reproduce

  1. Make the RPC request described in the description to a Base node running with op-reth
  2. Got Transaction conversion error

Node logs


Platform(s)

Linux (x86)

Container Type

LXC/LXD

What version/commit are you on?

reth-optimism-cli Version: 1.1.4
Commit SHA: 15fac08
Build Timestamp: 2024-12-11T10:16:37.504323039Z
Build Features: asm_keccak,jemalloc,optimism
Build Profile: maxperf

What database version are you on?

2024-12-17T07:17:38.727203Z INFO Initialized tracing, debug log directory: /root/.cache/reth/logs/dev
Current database version: 2
Local database version: 2

Which chain / network are you on?

--chain=base

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
@jonathanudd jonathanudd added C-bug An unexpected or incorrect behavior S-needs-triage This issue needs to be labelled labels Dec 17, 2024
Copy link
Contributor

github-actions bot commented Jan 8, 2025

This issue is stale because it has been open for 21 days with no activity.

@github-actions github-actions bot added the S-stale This issue/PR is stale and will close with no further activity label Jan 8, 2025
Copy link
Contributor

This issue was closed because it has been inactive for 7 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 16, 2025
@github-project-automation github-project-automation bot moved this from Todo to Done in Reth Tracker Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug An unexpected or incorrect behavior S-needs-triage This issue needs to be labelled S-stale This issue/PR is stale and will close with no further activity
Projects
Status: Done
Development

No branches or pull requests

1 participant