we are currently doing graphnode compatibility project,when we send request to arpc
curl -X POST https://arpc.apothem.network/ -H "Content-Type: application/json" -d '
{
"id": 1610,
"jsonrpc": "2.0",
"method": "eth_getLogs",
"params": [
{
"address": "0x53350795c11cee781a7e174479778f848d76ab2a",
"fromBlock": "0x22b2277",
"toBlock": "0x22b2277",
"topics": [
[
"0x8c5be1e5ebec7d5bd14f71427d1e84f3dd0314c0f7b2291e5b200ac8c7c3b925",
"0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef",
"0x6a12b3df6cba4203bd7fd06b816789f87de8c594299aed5717ae070fac781bac"
]
]
}
]
}'
it returns the following
{
"id": 1610,
"jsonrpc": "2.0",
"result": [
{
"address": "xdc53350795c11cee781a7e174479778f848d76ab2a",
"blockHash": "0x194a513ea40c94fccaca470cccb24c2ff3bd6398dec9a04e3eb3a4bfef8a330e",
"blockNumber": "0x22b2277",
"data": "0x000000000000000000000000000000000000000000084595161401484a000000",
"logIndex": "0x2",
"removed": false,
"topics": [
"0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef",
"0x0000000000000000000000000000000000000000000000000000000000000000",
"0x000000000000000000000000ce77393582d39048a4fc73770ab19d2b239c45dd"
],
"transactionHash": "0xbebc0bab1a0f9844b86b8edf3a169bb1eef9337ac8d2684d5ae758b6521c12fe",
"transactionIndex": "0x1"
}
]
}
and we found that the blockHash is 0x194a513ea40c94fccaca470cccb24c2ff3bd6398dec9a04e3eb3a4bfef8a330e which doesnt exist.
Anyone knows the reason?
Discussion (7)
btw, are you able to provide a bit more context on what you trying to achieve, as well as the values of the
topicsyou put in the parameters?we are trying to make it compatible with the graph
I'm not too sure what graph is or its relationship with XDC consensus engine.
Did you by any chance created a smart contract?
Basically try provide as much information/context as possible so that we can help identify the root cause
our enigneer said you just need to return the correct block hash
Even we are facing a similar issue , xdc.dev/ncode/block-not-found-erro...
Interesting. We will take a look shortly.
We have received your query, and the development team is working on the same.