erigon
erigon copied to clipboard
Tracing discrepancy between Bor and Erigon
Erigon version: v0.0.6 https://github.com/maticnetwork/erigon/releases/tag/v0.0.6
Commit hash: d9c5a01
Chain/Network: Polygon/Matic
When tracing on Polygon, the result is different between Bor and Erigon. While Bor has an output field for all the calls, Erigon does not.
This is the case with all the traces — CREATE/CREATE2/CALL/DELETECALL.

Example
{
"jsonrpc": "2.0",
"method": "debug_traceBlockByNumber",
"params": [
"0x27224F8",
{
"tracer": "callTracer",
"timeout": "120s"
}
],
"id": 1
}
- Bor - trace_41035000_bor.txt
- Erigon - trace_41035000_erigon.txt
Is this expected? Can this behavior be changed to make the outputs of both clients similar?
Looking into this
I checked on this and found that the response struct on erigon and bor (which is based on geth) is different, Hence bor is giving some extra fields in the response. Can you compare the same for erigon (for ethereum) and geth node ? I geth has also changed the values, Taking upstream changes in bor will fix the issue.
Well, I couldn't find that difference between Geth and Erigon (for Ethereum).

Here are the full traces:
- Geth
(1.11.5)- trace_17029941_geth.txt - Erigon
(2.42.0)- trace_17029941_erigon.txt
Thanks
So the output field is present in erigon as well in case of ethereum, Only in case of polygon you are not getting that output field ?
In case of Polygon-Erigon, yes, the output field is not present.
Thanks @a26nine for the confirmation. I will check if I can find the issue and will also share this with the community to seek help on this.
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.
(keep this open)
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.
(keep this open)
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.
keeping this open
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.
yperbasis changed Importance from Imp2 to Imp3
https://erigon.tech/an-update-on-our-support-for-polygon/