support both input and data in eth_call, eth_estimateGas, personal_sendTransaction

[JukLee0ira]

Proposed changes

A user reported a bug in here when using the Go-Ethereum client to call JSON-RPC. The issue arises because the parameter field 'data' has been renamed to 'input' from version 1.13 onwards.

This PR adds support of "input" field in eth_call,eth_estimateGas . Field "data" will be still supported

Test

When this PR is not merged:

• For RPC="http://127.0.0.1:8545", the changes from this PR are applied.
• For RPC="https://arpc.apothem.network/", the changes from this PR are not applied.

eth_call

• data field

Request:

RPC="http://127.0.0.1:8545"
curl -s -X POST -H "Content-Type: application/json" ${RPC} -d '{
  "jsonrpc": "2.0",
  "id": 8001,
  "method": "eth_call",
  "params": [
    {
      "to": "0x0000000000000000000000000000000000000088",
      "data": "0x0db02622"
    },
    "latest"]}' | jq

Response:

{
  "jsonrpc": "2.0",
  "id": 8001,
  "result": "0x000000000000000000000000000000000000000000000000000000000000000b"
}

• input field

Request:

RPC="https://arpc.apothem.network/"
curl -s -X POST -H "Content-Type: application/json" ${RPC} -d '{
  "jsonrpc": "2.0",
  "id": 8001,
  "method": "eth_call",
  "params": [
    {
      "to": "0x0000000000000000000000000000000000000088",
      "input": "0x0db02622"
    },
    "latest"]}' | jq

Response:

{
  "jsonrpc": "2.0",
  "id": 8001,
  "error": {
    "code": -32000,
    "message": "execution reverted"
  }
}

---

Request:

RPC="http://127.0.0.1:8545"
curl -s -X POST -H "Content-Type: application/json" ${RPC} -d '{
  "jsonrpc": "2.0",
  "id": 8001,
  "method": "eth_call",
  "params": [
    {
      "to": "0x0000000000000000000000000000000000000088",
      "input": "0x0db02622"
    },
    "latest"]}' | jq

Response:

{
  "jsonrpc": "2.0",
  "id": 8001,
  "result": "0x000000000000000000000000000000000000000000000000000000000000000b"
}

• Requests that include both an input field and a data field, and these fields have the same value.

Request:

RPC="http://127.0.0.1:8545"
curl -s -X POST -H "Content-Type: application/json" ${RPC} -d '{
  "jsonrpc": "2.0",
  "id": 8001,
  "method": "eth_call",
  "params": [
    {
      "to": "0x0000000000000000000000000000000000000088",
      "input": "0x0db02622",
      "data": "0x0db02622"
    },
    "latest"]}' | jq

Response:

{
  "jsonrpc": "2.0",
  "id": 8001,
  "result": "0x000000000000000000000000000000000000000000000000000000000000000b"
}

• Requests that include both an input field and a data field, but these fields have different values.

Request:

RPC="http://127.0.0.1:8545"
curl -s -X POST -H "Content-Type: application/json" ${RPC} -d '{
  "jsonrpc": "2.0",
  "id": 8001,
  "method": "eth_call",
  "params": [
    {
      "to": "0x0000000000000000000000000000000000000088",
      "input": "0x0db02622",
      "data": "0x12345678"
    },
    "latest"]}' | jq

Response:

{
  "jsonrpc": "2.0",
  "id": 8001,
  "result": "0x000000000000000000000000000000000000000000000000000000000000000b"
}

eth_estimateGas

• data field

Request:

RPC="http://127.0.0.1:8545"
curl -s -X POST -H "Content-Type: application/json" ${RPC} -d '{
  "jsonrpc": "2.0",
  "id": 8001,
  "method": "eth_estimateGas",
  "params": [
    {
      "to": "0x0000000000000000000000000000000000000088",
      "data": "0x0db02622"
    },
    "latest"]}' | jq

Response:

{
  "jsonrpc": "2.0",
  "id": 8001,
  "result": "0x574a"
}

• input field

Request:

RPC="https://arpc.apothem.network/"
curl -s -X POST -H "Content-Type: application/json" ${RPC} -d '{
  "jsonrpc": "2.0",
  "id": 8001,
  "method": "eth_estimateGas",
  "params": [
    {
      "to": "0x0000000000000000000000000000000000000088",
      "input": "0x0db02622"
    },
    "latest"]}' | jq

Response:

{
  "jsonrpc": "2.0",
  "id": 8001,
  "error": {
    "code": -32000,
    "message": "execution reverted"
  }
}

---

Request:

RPC="http://127.0.0.1:8545"
curl -s -X POST -H "Content-Type: application/json" ${RPC} -d '{
  "jsonrpc": "2.0",
  "id": 8001,
  "method": "eth_estimateGas",
  "params": [
    {
      "to": "0x0000000000000000000000000000000000000088",
      "input": "0x0db02622"
    },
    "latest"]}' | jq

Response:

{
  "jsonrpc": "2.0",
  "id": 8001,
  "result": "0x574a"
}

• Requests that include both an input field and a data field, and these fields have the same value.

Request:

RPC="http://127.0.0.1:8545"
curl -s -X POST -H "Content-Type: application/json" ${RPC} -d '{
  "jsonrpc": "2.0",
  "id": 8001,
  "method": "eth_estimateGas",
  "params": [
    {
      "to": "0x0000000000000000000000000000000000000088",
      "input": "0x0db02622",
      "data": "0x0db02622"
    },
    "latest"]}' | jq

Response:

{
  "jsonrpc": "2.0",
  "id": 8001,
  "result": "0x574a"
}

• Requests that include both an input field and a data field, but these fields have different values.

Request:

RPC="http://127.0.0.1:8545"
curl -s -X POST -H "Content-Type: application/json" ${RPC} -d '{
  "jsonrpc": "2.0",
  "id": 8001,
  "method": "eth_estimateGas",
  "params": [
    {
      "to": "0x0000000000000000000000000000000000000088",
      "input": "0x0db02622",
      "data": "0x12345678"
    },
    "latest"]}' | jq

Response:

{
  "jsonrpc": "2.0",
  "id": 8001,
  "result": "0x574a"
}

Types of changes

What types of changes does your code introduce to XDC network?
Put an ✅ in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)
• Regular KTLO or any of the maintaince work. e.g code style
• CICD Improvement
• N/A

Impacted Components

Which part of the codebase this PR will touch base on,

Put an ✅ in the boxes that apply

• Consensus
• Account
• Network
• Geth
• Smart Contract
• External components
• Not sure (Please specify below)

Checklist

Put an ✅ in the boxes once you have confirmed below actions (or provide reasons on not doing so) that

• This PR has sufficient test coverage (unit/integration test) OR I have provided reason in the PR description for not having test coverage
• Provide an end-to-end test plan in the PR description on how to manually test it on the devnet/testnet.
• Tested the backwards compatibility.
• Tested with XDC nodes running this version co-exist with those running the previous version.
• Relevant documentation has been updated as part of this PR
• N/A

[gzliudan]

Please use code format for request and json format for response, such as:

```shell
// request code
```
 
```json
// response text
```

[gzliudan]

LGTM