-
Notifications
You must be signed in to change notification settings - Fork 5k
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
signTransaction fails with Method eth_chainId not supported. (beta51) #2610
Comments
This isn't an issue of Web3.js and there is already an open issue in the ganache repository: trufflesuite/ganache#339. |
@nivida : |
Any update on this? This is still an issue in web3 |
Why is this closed? I am receiving this error and I don't even use Truffle |
But probably the implementation should determine this when the provider is set; I think it's always a 1:1 relationship. |
@prographo according to this, it is not 1-1, even empirically: https://medium.com/@pedrouid/chainid-vs-networkid-how-do-they-differ-on-ethereum-eec2ed41635b |
Can anyone help me here: My system versions are: |
Description
signTransaction fails with
Method eth_chainId not supported.
error when I don't providechainId
in tx data. It used to work in earlier beta releases.It seems the defaults are not passed through because when I provide
chainId
in the tx data then sign complains about the gas being too low.It's a regression, it works fine in beta36.
Expected behavior
This should work without passing
chainId
orgas
(with defaultGas)Actual behavior
the code above throws:
Method eth_chainId not supported.
if I include
chainId
then I receive:Error: TransactionSigner Error: gas limit is too low. Need at least 53464
Steps to reproduce the behavior
Error Logs
When I don't provide chainId:
When I provide
chainId
but notgas:
Gists
https://github.com/Augmint/web3js_integration_tests/blob/master/test/signTransaction.js
Versions
The text was updated successfully, but these errors were encountered: