lotus/chain/types/ethtypes
Steven Allen 156a3a400c
fix: Eth API: accept input data in call arguments under field 'input' (#11505)
The correct name for this field is 'input' according to the Ethereum specs [0].
However, for the longest time, clients have been using 'data' and servers have been
lenient to accept both, preferring 'input' over 'data' when both appear.

Our lack of support for 'input' had gone unnoticed until go-ethereum decided
to adjust their ethclient implementation to issue eth_call and eth_estimateGas
requests with the 'input' field instead of 'data' [1]. This suddenly broke apps
using this client against Lotus' Eth API.

[0]: https://github.com/ethereum/execution-apis/blob/main/src/schemas/transaction.yaml#L33-L35
[1]: ethereum/go-ethereum#28078

Co-authored-by: raulk <raul.kripalani@gmail.com>
2024-01-06 15:42:52 -08:00
..
eth_transactions_test.go remove invalid test cases 2023-01-14 12:30:06 -05:00
eth_transactions.go fix: eth: use the correct state-tree when resolving addresses (#11387) 2023-11-17 18:20:31 +01:00
eth_types_test.go fix: Eth API: accept input data in call arguments under field 'input' (#11505) 2024-01-06 15:42:52 -08:00
eth_types.go fix: Eth API: accept input data in call arguments under field 'input' (#11505) 2024-01-06 15:42:52 -08:00
rlp_test.go fix: ethtypes: handle length overflow case 2023-07-21 12:26:29 -04:00
rlp.go fix: ethtypes: handle length overflow case 2023-07-21 12:26:29 -04:00