search

ethereum / execution-apis

Collection of APIs provided by Ethereum execution layer clients
Creative Commons Zero v1.0 Universal
908 stars 352 forks source link

`data` vs `input` in `eth_call` params #507

Closed Amit0617 closed 5 months ago

Amit0617 commented 6 months ago

Original specs mention input as one of the key of object, and that's simply inherited from specs mentioned in this repo. I had originally faced this issue for eth_sendTransaction which turned out to be a wallet method not part of the core Ethereum protocol. Besides, this issue was already raised earlier. Request of removal was also proposed. Even if eth_sendTransaction is removed in future from the docs, eth_call still needs to be corrected. I have verified this using Hardhat rpc url, following are the screenshots trying eth_call using inspector given in official docs. When input key is provided, it reverts without a reason 2024-01-02-15-24-45

When data key is provided, it succeeds.

2024-01-02-15-24-58

shanejonas commented 6 months ago

👍

Would love to get this solved

fjl commented 5 months ago

It's an issue with the wallet. They should support input because it is in the spec.

lightclient commented 5 months ago

I would open this issue in hardhat.

Amit0617 commented 3 months ago

ethereum.CallMsg should also have it as Input probably.