-
Notifications
You must be signed in to change notification settings - Fork 40
Open
Description
Hello, comparing Flare with Avalanche, the debug_traceBlockByNumber JSON-RPC call is missing the txHash from the response. I've included the curl commands with a small example to show the response.
Fix needed is to include the txHash as part of the response payload
curl https://docs-demo.flare-mainnet.quiknode.pro/ext/bc/C/rpc \
-X POST \
-H "Content-Type: application/json" \
--data '{"method":"debug_traceBlockByNumber","params":["0x251da47", {"tracer": "callTracer"}],"id":1,"jsonrpc":"2.0"}' | jq | grep -c txHash
Above returns 0 matches (But does return a response with traces)
curl https://docs-demo.avalanche-mainnet.quiknode.pro/ext/bc/C/rpc \
-X POST \
-H "Content-Type: application/json" \
--data '{"method":"debug_traceBlockByNumber","params":["0x382dfcc", {"tracer": "callTracer"}],"id":1,"jsonrpc":"2.0"}' | jq | grep -c txHash
Whereas Avalanche returns the below returns 7
Below is an excerpt from the Avalanche response
"txHash": "0xbc041f68f0445bb617415ca1164f522a9f4cdab8945640537c0e8069350e56f0",
"result": {
"from": "0x039a5562a11fc7cc38fe118a6f0a6512d49ebaf2",
"gas": "0x16e360",
"gasUsed": "0x70e6",
"input": "0x61a3dd871a2c20157020f7cbe883b3ca93c57e6a2429036602b5ed1172f682acd32cab9a109e8b5ae8369e4c8070e0f0d1ebb76a889e2e1f17ee8081c3fc39586a62cafe000000000000000000000000000000000000000000000000000000000382dfc7000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000c3500000000000000000000000000000000000000000000000000000000000000000100000000000000000000000008e1e965b485ed4f8f4e4b32bc65bbbe5f302d72",
"output": "0x0000000000000000000000000000000000000000000000000000000000000001",
"to": "0x4bef02f3dac22707fcb0aa054962fd4d2041726d",
"type": "CALL",
"value": "0x0"
}
}
Metadata
Metadata
Assignees
Labels
No labels