JSONRPC: eth_call proceed 'input' field unexpectedly for view functions

[topcai]

According to JSON-RPC spec( https://ethereum.github.io/execution-apis/api-documentation/ ), eth_call accepts 'input' as a parameter.

However, calling eth_call for contract view functions with 'input' filed instead of 'data' filed, the RPC returned 'execution reverted'. Replace 'input' with 'data' works.

Reproduce step for testnet:
non-working: {"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"from":"0x0000000000000000000000000000000000000000","input":"0x54fd4d50","to":"0x40d046f41b6e161909054c0f3ae075199d363c23"},"latest"]}
working: {"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"from":"0x0000000000000000000000000000000000000000","data":"0x54fd4d50","to":"0x40d046f41b6e161909054c0f3ae075199d363c23"},"latest"]}

[topcai]

found the cause. it is because silkworm rpc ignores 'input' filed and set 'data' as empty bytes when there's no 'data' filed present