Discrepancy in response between bor vs erigon for eth_getLogs on polygon amoy
System information
Bor client version: [e.g. v0.2.16]
bor v2.0.2 erigon v3.0.3
Heimdall client version: [e.g. v0.2.10]
heimdall v1.2.3
OS & Version: Linux ubuntu 22.04
Environment: Polygon Amoy
Type of node: bor (full) erigon (archive)
Additional Information:
Overview of the problem
request
{
"id": 1,
"jsonrpc": "2.0",
"method": "eth_getLogs",
"params": [
{
"fromBlock": "0x4948e0",
"toBlock": "0x4948e0",
"topics": [
"0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"
]
}
]
}
bor
{
"jsonrpc": "2.0",
"id": 1,
"result": [
{
"address": "0x3e5542c1649e77cdbbd7ecdebf82b400536f1f99",
"topics": [
"0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef",
"0x0000000000000000000000000000000000000000000000000000000000000000",
"0x0000000000000000000000003c52d281d2e0297068c4b56bf509ec1ebafe86b1"
],
"data": "0x0000000000000000000000000000000000000000000000004563918244f40000",
"blockNumber": "0x4948e0",
"transactionHash": "0x0a1347df48ab94b43ecf7590f0e7d992b46a3c8188d4aa23d7e6a774669c3c69",
"transactionIndex": "0x0",
"blockHash": "0x155b536cde08b9c7bfbcb24eb4d28911eef5c3853618e2a2721c08eafd2f7da1",
"logIndex": "0x0",
"removed": false
}
]
}
erigon
{
"jsonrpc": "2.0",
"id": 1,
"result": [
{
"address": "0x3e5542c1649e77cdbbd7ecdebf82b400536f1f99",
"topics": [
"0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef",
"0x0000000000000000000000000000000000000000000000000000000000000000",
"0x0000000000000000000000003c52d281d2e0297068c4b56bf509ec1ebafe86b1"
],
"data": "0x0000000000000000000000000000000000000000000000004563918244f40000",
"blockNumber": "0x4948e0",
"transactionHash": "0x0a1347df48ab94b43ecf7590f0e7d992b46a3c8188d4aa23d7e6a774669c3c69",
"transactionIndex": "0x0",
"blockHash": "0x155b536cde08b9c7bfbcb24eb4d28911eef5c3853618e2a2721c08eafd2f7da1",
"logIndex": "0x0",
"removed": false
},
{
"address": "0x52ef3d68bab452a294342dc3e5f464d7f610f72e",
"topics": [
"0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef",
"0x0000000000000000000000000000000000000000000000000000000000000000",
"0x00000000000000000000000091af3393baa7dfce0d83e38eeea37765dab70f0c"
],
"data": "0x000000000000000000000000000000000000000000000000002386f26fc10000",
"blockNumber": "0x4948e0",
"transactionHash": "0xf49fe59805106ad10fe20484574a8447bebff57317ab7c20f72b55f6c3db8f6a",
"transactionIndex": "0x1",
"blockHash": "0x155b536cde08b9c7bfbcb24eb4d28911eef5c3853618e2a2721c08eafd2f7da1",
"logIndex": "0x0",
"removed": false
}
]
}
Reproduction Steps
Submit request to bor and erigon nodes running polygon amoy
Hi @web3-nodeops,
Thanks for letting us know. We will look on this and update you as soon as we find the issue. But in a first look, it seems it's missing something on include some POL txs into this filter.
This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 14 days.
This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 14 days.
This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 14 days.
Hi @web3-nodeops , the issue is probably that you node not enabled the "bor.logs" flag. So please include it on your start command or in the config.toml file.