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
When using a recent version of geth, the data returned by eth_feeHistory can't be parsed due to using hex notation for the baseFeePerBlobGas field. I tried running a forge script invocation with RUST_LOG=trace and received the following error:
This was fixed in alloy recently, so updating the dependencies should be good enough alloy-rs/alloy#722
Reproducible by running a recent version of geth (geth version 1.14.2-stable-35b2d07f in my case).
#!/bin/sh
# start geth in the background so that we can prefund our dev account
geth --http --http.port 8545 --dev --http.api eth,web3,net,debug --gcmode=archive &
sleep 10
# prefund our dev account
geth attach --exec 'eth.sendTransaction({from: eth.accounts[0], to: "0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266", value: web3.toWei(50, "ether")})' /tmp/geth.ipc
cast send $(cast address-zero) --value 1 --mnemonic "test test test test test test test test test test test junk"
wait
Fails with
Error:
deserialization error: invalid number at line 1 column 168
Context:
- invalid number at line 1 column 168
The text was updated successfully, but these errors were encountered:
Component
Forge, Cast
Have you ensured that all of these are up to date?
What version of Foundry are you on?
forge 0.2.0 (a470d63 2024-05-16T00:17:19.757926135Z)
What command(s) is the bug in?
forge script, cast send, likely more
Operating System
Linux
Describe the bug
When using a recent version of geth, the data returned by
eth_feeHistory
can't be parsed due to using hex notation for thebaseFeePerBlobGas
field. I tried running aforge script
invocation withRUST_LOG=trace
and received the following error:This was fixed in alloy recently, so updating the dependencies should be good enough alloy-rs/alloy#722
Reproducible by running a recent version of geth (
geth version 1.14.2-stable-35b2d07f
in my case).Fails with
The text was updated successfully, but these errors were encountered: