Hardhat Node does not support "input" as field for eth_call input

[rzmahmood]

Version of Hardhat

2.19.1

What happened?

The go-ethereum team switched to using input instead of data in their transaction objects in ethclient. This caused our eth_calls to break since hardhat does not expect input. Ideally hardhat node can support both fields.

Hardhat node will instead just set the data field to 0x which will cause most eth_calls to revert with error Transaction reverted without a reason string

Their PR: ethereum/go-ethereum#28078

Minimal reproduction steps

Make a transaction where the data payload is using field input instead of data.

Search terms

No response

[rzmahmood]

Duplicate of #4438

Feel free to close, but would like visibility on this

[schaable]

Closing as duplicate.