-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Weird error when sending a Tx with cast #1866
Comments
I've run into this as well. FWIW, I was able to reproduce the issue with |
oh, sorry about that, that's an oversight gakonst/ethers-rs#1356 will fix this |
@mattsse I updated to the very last version with foundryup and retested, and I still have the same problem/error |
fixes: foundry-rs/foundry#1866, because previously we'd read chain id 31337, parse it as Dev, and then when convert it to the wrong number (1337) which would make the transaction's chain id not match the signer's
fixes: foundry-rs/foundry#1866, because previously we'd read chain id 31337, parse it as Dev, and then when convert it to the wrong number (1337) which would make the transaction's chain id not match the signer's
Component
Cast
Have you ensured that all of these are up to date?
What version of Foundry are you on?
forge 0.2.0 (3fc1491 2022-06-06T00:12:33.657656525Z)
What command(s) is the bug in?
cast send --rpc-url=$RPC_URL --private-key=$PRIVATE_KEY
Operating System
Linux
Describe the bug
When sending the following Tx on a local Anvile node:
cast send --rpc-url=$RPC_URL --private-key=$PRIVATE_KEY --value 0.08ether 0x5fbdb2315678afecb367f032d93f642f64180aa3 "mintTo(address)" 0xf39fd6e51aad88f6f4ce6ab8827279cfffb92266
The following error is raised:
The text was updated successfully, but these errors were encountered: