-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Deployer error: only replay-protected (EIP-155) transactions allowed over RPC #3935
Comments
This issue might also manifests as when trying to migrate your contracts to infura
If you are stuck on this and don't know what to do, try deploying your contracts with remix. Interaction with truffle should work (with the latest master) only deployment is broken |
Master (v5.2.5 released yesterday) does not solve this issue when trying to deploy with infura or alchemy, deploying with remix did work however. |
Probably a dupe of #3913. |
I can confirm I have the same issue. I try to deploy my contract to ropsten, all parameters set with enough eth in the right address, and get the 'invalid sender' error.
I've checked everything, my truffle-config.js file is correct. using Truffle v5.2.5 |
Stuck with the same issue! Is there a fix for the error ? |
@noahfigueras Fix is to downgrade |
Thanks @maxwellfortney I downgraded @truffle/[email protected] and it deploys correctly now! |
Question, are these problems still happening on Truffle 5.2.6? Thank you! |
@haltman-at Yes. I couldn't deploy a contract now. Downgrading a @truffle/hdwallet-provider is helped for me. |
I was getting |
@shoenseiwaso Is a fix as simple as just adding the chainid key to the eventArgs object in truffle/packages/deployer/src/deployment.js Line 278 in 500fdcc
In here: truffle/packages/deployer/src/deployment.js Lines 309 to 320 in 500fdcc
|
Possible dup of #3946. |
Could someone provide me with a simple project and detailed steps to reproduce this error? It would be really helpful to have to test against. |
@eggplantzzz Any project migrating against you own geth node (v1.10.1 and higher) with |
@MariusVanDerWijden It would be helpful if you have a specific project. I am able to successfully migrate a toy project to Geth version 1.10.1-stable using the currently released version of Truffle. If you have one handy and specific steps, I would appreciate it! |
@eggplantzzz repo which reproduces the issue is here. Follow the steps in the README: |
Thanks for providing the repro steps! I was able to recreate the error - it looks like upgrading |
This should be fixed in Truffle v5.3.0. Closing optimistically, but let us know if the problem persists, and we'll be glad to re-open! Thanks all! |
@eggplantzzz @gnidan Truffle v5.3.0 did indeed fix the issue. However, upgrading Truffle alone was not enough: I also had to upgrade the Is it worth putting a note in the v5.3.0 release notes?
|
Note that the fix did not address the case where the network ID and chain ID differ. Opened #3961 for this. |
it work now |
Other Solution Inside truffle-config.js use : const HDWalletProvider = require('truffle-hdwallet-provider'); instead of const HDWalletProvider = require('@truffle/hdwallet-provider'); It's just other way of downgrading the @truffle/hdwallet-provider while your package.json can still have |
Since the upgrade to 1.10, the chain ID is now a required parameter. Although #3923 was merged to address it in the contract package, the deployer seems to be broken. The issue might be in executeDeployment(), where chain ID is not set.
Running
truffle migrate --reset
we see:The text was updated successfully, but these errors were encountered: