Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't send EIP-4844 tx from alloy client to reth node #8503

Closed
1 task done
StackOverflowExcept1on opened this issue May 30, 2024 · 0 comments · Fixed by #8506
Closed
1 task done

Can't send EIP-4844 tx from alloy client to reth node #8503

StackOverflowExcept1on opened this issue May 30, 2024 · 0 comments · Fixed by #8506
Labels
A-rpc Related to the RPC implementation C-bug An unexpected or incorrect behavior

Comments

@StackOverflowExcept1on
Copy link

StackOverflowExcept1on commented May 30, 2024

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:

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"}'

Node logs

No response

Platform(s)

Linux (x86)

What version/commit are you on?

root@e94dd28f6e2f:/# reth --version
reth Version: 0.2.0-beta.7
Commit SHA: a44e085
Build Timestamp: 2024-05-09T21:04:29.696046697Z
Build Features: jemalloc
Build Profile: maxperf

What database version are you on?

root@e94dd28f6e2f:/# reth db version
Current database version: 2
Local database is uninitialized

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

  • I agree to follow the Code of Conduct
@StackOverflowExcept1on StackOverflowExcept1on added C-bug An unexpected or incorrect behavior S-needs-triage This issue needs to be labelled labels May 30, 2024
@mattsse mattsse added A-rpc Related to the RPC implementation and removed S-needs-triage This issue needs to be labelled labels May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-rpc Related to the RPC implementation C-bug An unexpected or incorrect behavior
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants