Description:
I am running two versions of Nethermind:
Version 1.26.0
Version 1.30.3 or even latest version 1.31.0
When querying transaction details using eth_getTransactionByHash, the response from version 1.30.3 is missing the gasPrice and v fields, while the response from 1.26.0 includes them.
Steps to Reproduce:
-
Run Nethermind node on version 1.30.3.
-
Execute the following curl command:
curl -X POST <MY-RPC-URL> -H "Content-Type: application/json" \
--data '{"jsonrpc":"2.0","method":"eth_getTransactionByHash","params":["0x99893d2faf08db38b1c6ca5fc72c2f1fecf50c36f022ba1fe6363249f34890e3"],"id":1}'
- Compare the response with the same query on version 1.26.0.
Expected Behavior:
- The response should include gasPrice and v fields, as seen in version 1.26.0.
Actual Behavior:
gasPrice and v are missing in version 1.30.3. and 1.31.0
Example Response (1.26.0 - Correct):
{
"jsonrpc": "2.0",
"result": {
"gasPrice": "0xea45df12",
"v": "0x1",
...
},
"id": 1
}
Example Response (1.30.3 - Incorrect):
{
"jsonrpc": "2.0",
"result": {
...
},
"id": 1
}
There is no feild of gasPrice or v
Environment:
Additional Context:
-
The issue persists across multiple transactions.
-
The nodes are fully synced.
-
No relevant error logs observed.
Possible Causes:
Suggested Fix:
- Ensure
gasPrice and v fields are included in eth_getTransactionByHash responses for backward compatibility.
Description:
I am running two versions of Nethermind:
Version 1.26.0
Version 1.30.3 or even latest version 1.31.0
When querying transaction details using eth_getTransactionByHash, the response from version 1.30.3 is missing the
gasPriceandvfields, while the response from 1.26.0 includes them.Steps to Reproduce:
Run Nethermind node on version 1.30.3.
Execute the following curl command:
Expected Behavior:
Actual Behavior:
gasPriceandvare missing in version 1.30.3. and 1.31.0Example Response (1.26.0 - Correct):
Example Response (1.30.3 - Incorrect):
There is no feild of
gasPriceorvEnvironment:
Nethermind Version: 1.30.3
Sync Mode: Full
OS: Ubuntu 22.04
Additional Context:
The issue persists across multiple transactions.
The nodes are fully synced.
No relevant error logs observed.
Possible Causes:
Change in Nethermind's handling of transaction fields.
RPC output formatting differences between versions.
Suggested Fix:
gasPriceandvfields are included ineth_getTransactionByHashresponses for backward compatibility.