You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you may know, the alloy client has an automatic calculation of transaction fees if you use the recommended filters. So, I looked at the client's alloy logs and found the problematic request. It seems eth_feeHistory works somehow differently on nodes like geth.
Client logs:
TRACE alloy_rpc_client::call: serialized request request={"method":"eth_feeHistory","params":["0xa","latest",[20.0]],"id":1,"jsonrpc":"2.0"}
TRACE alloy_transport_ws: received message from websocket text={"jsonrpc":"2.0","error":{"code":-32602,"message":"Invalid params","data":"invalid type: string \"0xa\", expected u64 at line 1 column 5"},"id":1}
Steps to reproduce
# OK
curl https://ethereum-holesky-rpc.publicnode.com \
-X POST \
-H "Content-Type: application/json" \
--data '{"method":"eth_feeHistory","params":["0xa","latest",[20.0]],"id":1,"jsonrpc":"2.0"}'# ERR
RETH_RPC_URL="<insert_rpc_here>"
curl $RETH_RPC_URL \
-X POST \
-H "Content-Type: application/json" \
--data '{"method":"eth_feeHistory","params":["0xa","latest",[20.0]],"id":1,"jsonrpc":"2.0"}'
Describe the bug
As you may know, the alloy client has an automatic calculation of transaction fees if you use the recommended filters. So, I looked at the client's alloy logs and found the problematic request. It seems eth_feeHistory works somehow differently on nodes like geth.
Client logs:
Steps to reproduce
Node logs
No response
Platform(s)
Linux (x86)
What version/commit are you on?
What database version are you on?
Which chain / network are you on?
Holesky
What type of node are you running?
Archive (default)
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: