erigon icon indicating copy to clipboard operation
erigon copied to clipboard

`trace_block` method not working as expected in version 2.48.1

Open luarx opened this issue 1 year ago • 2 comments

System information

Previus Erigon version that we were using so far: 2.42.0 New Erigon version that we want to use: 2.48.1 (this is the version that does not work as expected, we do not know if the bug was present in previous ones between 2.42.0 and 2.48.1.

OS & Version: Linux (Docker)

Erigon Command (with flags/config):

            "--chain=mainnet",
            "--metrics",
            "--metrics.addr=0.0.0.0",
            "--metrics.port=6060",
            "--private.api.addr=0.0.0.0:9089",
            "--pprof",
            "--pprof.addr=0.0.0.0",
            "--pprof.port=6061",
            "--snapshots=true",
            "--http",
            "--http.api=engine,net,eth,debug,trace,txpool,web3",
            "--http.addr=0.0.0.0",
            "--http.port=8545",
            "--http.vhosts=*",
            "--http.corsdomain=*",
            "--authrpc.addr=0.0.0.0",
            "--authrpc.jwtsecret=/mnt/jwtsecret/jwtsecret",
            "--authrpc.port=9545",
            "--authrpc.vhosts=*",
            "--prune=", 
            "--rpc.batch.limit=1000",
            "--rpc.returndata.limit=500000",
            "--trace.maxtraces=5000000"

Concensus Layer: v2.3.0

Concensus Layer Command (with flags/config):

              "--debug-level=info",
              "--datadir=/beacondata",
              "--network=mainnet",
              "beacon_node",
              "--disable-enr-auto-update",
              "--enr-address=127.0.0.1",
              "--enr-tcp-port=9000",
              "--enr-udp-port=9000",
              "--port=9000" ,
              "--discovery-port=9000",
              "--eth1",
              "--http",
              "--http-address=0.0.0.0",
              "--http-port=5052",
              "--metrics",
              "--metrics-address=0.0.0.0",
              "--metrics-port=5054",
              "--listen-address=0.0.0.0",
              "--target-peers=100",
              "--http-allow-sync-stalled",
              "--disable-packet-filter",
              "--execution-endpoint=http://localhost:9545",
              "--jwt-secrets=/tmp/jwtsecret",
              "--disable-deposit-contract-sync"

Chain/Network: mainnet

Expected behaviour

Execute trace_block to block 15630274 (mainnet) - It returns 503 elements

Actual behaviour

Execute trace_block to block 15630274 (mainnet) - It returns 502 elements

Steps to reproduce the behaviour

Backtrace

[backtrace]

luarx avatar Jul 28 '23 10:07 luarx

This is a duplicate of #7827, conclusion of which is: post-merge block rewards are no longer being returned as zero-value reward traces.

Starting from the merge (block number >= 15537394) value for these traces is 0x0:

{
  "action": {
    "author": "0xeee27662c2b8eba3cd936a23f039f3189633e4c8",
    "rewardType": "block",
    "value": "0x0"
  },
  "blockHash": "0x56a9bb0302da44b8c0b3df540781424684c3af04d0b7a38d72842b762076a664",
  "blockNumber": 15537394,
  "result": null,
  "subtraces": 0,
  "traceAddress": [],
  "type": "reward"
}

So the above is returned in trace_block results by v2.42.0, but not by v2.47.0+. Trace results for pre-Merge blocks should look the same, i.e block 15537393 has 4 total traces in both Erigon versions, and the trace reward has non-zero value:

{
  "action": {
    "author": "0x829bd824b016326a401d083b33d092293333a830",
    "rewardType": "block",
    "value": "0x1bc16d674ec80000"
  },
  "blockHash": "0x55b11b918355b1ef9c5db810302ebad0bf2544255b530cdce90674d5887bb286",
  "blockNumber": 15537393,
  "result": null,
  "subtraces": 0,
  "traceAddress": [],
  "type": "reward"
}

ttibord avatar Sep 06 '23 15:09 ttibord

This issue is stale because it has been open for 40 days with no activity. Remove stale label or comment, or this will be closed in 7 days.

github-actions[bot] avatar Oct 17 '23 02:10 github-actions[bot]