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

besu node rpc returns data exception #39

Open
rayn316 opened this issue Mar 21, 2024 · 8 comments
Open

besu node rpc returns data exception #39

rayn316 opened this issue Mar 21, 2024 · 8 comments
Assignees
Labels

Comments

@rayn316
Copy link

rayn316 commented Mar 21, 2024

os: ubuntu 22.04
network: mainnet
bin: ./besu-24.3.0/bin/besu --config-file=/node/full/linea/bin/config-mainnet.toml

There is a problem with besu software debug_traceBlockByHash debug_traceBlockByNumber. Compared with geth, the data returned is abnormally large at certain times.
besu returns 200MB+ data (Some blocks are even larger)
geth returns 92KB data

curl --location --request POST '127.0.0.1:8545' \
--header 'Content-Type: application/json' \
--data-raw '{"method":"debug_traceBlockByHash","params":["0x908dc81be1f01948e7c002407e36c8401bf301d48e979e04a512e7513af79d13", {"tracer": "callTracer"}],"id":1,"jsonrpc":"2.0"}'

image

@daniellehrner daniellehrner self-assigned this Mar 21, 2024
@Gabriel-Trintinalia
Copy link

Maybe disableMemory could help?

@rayn316
Copy link
Author

rayn316 commented Apr 1, 2024

How to disable Memory
I don’t see it in the command help, what should I do?

@Gabriel-Trintinalia
Copy link

Gabriel-Trintinalia commented Apr 1, 2024

@rayn316 You can check the tracer config here: https://besu.hyperledger.org/public-networks/reference/api#debug_traceblockbynumber

{
   "jsonrpc":"2.0",
   "method":"debug_traceBlockByHash",
   "params":[
      "0x908dc81be1f01948e7c002407e36c8401bf301d48e979e04a512e7513af79d13",
      {
         "disableMemory":true
      }
   ],
   "id":1
}

@rayn316
Copy link
Author

rayn316 commented Apr 2, 2024

There is still a problem in the return. After turning on disableMemory, it is still very large. After turning off all three projects, the data is all meaningless.

curl -Ls -X POST -H 'Content-Type: application/json' -d '{
   "jsonrpc":"2.0",
   "method":"debug_traceBlockByHash",
   "params":[
      "0x0db7b4ae8fe16ddbeb676e0cfdcb2728f0eac64d25905e0887b178edf619fae4",
      {
         "disableMemory":true,
         "disableStorage":true,
         "disableStack":true
      }
   ],
   "id":1
}' 'http://127.0.0.1:8545'

image
image
image

@Gabriel-Trintinalia
Copy link

Gabriel-Trintinalia commented Apr 2, 2024

@rayn316 Could you please post what you are seeing with Geth?

@rayn316
Copy link
Author

rayn316 commented Apr 2, 2024

image
info.txt

@manofthemooon
Copy link

Issue with the size of the data returned by the debug_traceBlockByHash and debug_traceBlockByNumber methods in Besu compared to Geth, particularly when dealing with certain blocks. While Geth returns data in the range of kilobytes, Besu returns significantly larger data, sometimes exceeding 200MB.

Copy link

This issue is stale because it has been open for 6 months with no activity.

@github-actions github-actions bot added the Stale label Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants