-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Truffle migrate cannot handle a network ID different from the chain ID #3961
Comments
This is a problem for compatibility with other EVM-based chains that use Truffle. I'm getting reports from users that the latest EIP-155 change broke compatibility with Avalanche and our Fuji testnet. |
Same Problem here but I get following message: `
|
Having the same problem. Definitely using the right chain ID (kovan:42) and tried both Aave v.1 and v.2 lendingpooladdressprovider addresses, but no dice. |
HD-wallet seems to be an issue. |
Hmpf.. Im trying to migrate a contract since 3 days but not working.. |
Yeah same |
There is a fix in this PR |
@truffle/hdwallet-provider version 1.4.0 has just been released and I think it will solve this issue. Can you try it out and confirm or deny that it fixes the problem? Thanks! |
I can test today |
Confirmed fixed using the repro repo, thanks! |
#4019 fixed the 'wrong chainId" issue for me. Thank you very much! |
Glad to hear it! |
Issue
@eggplantzzz @gnidan I think we found another corner case: no version of Truffle works if the chain ID is different from the network ID (i.e., I tried earlier versions than 5.3.0 as well).
Related/possibly related: #3935, #3957, #3953, #3949, #3946
Steps to Reproduce
Follow the steps in the README in this repo. Note that it has been updated for this issue since #3935 - please do a
git pull
if you had previously cloned it.https://github.com/curvegrid/truffle-eip155-issues
Expected Behavior
Migration completes successfully.
Actual Results
Environment
truffle version
): Truffle v5.3.0 (core: 5.3.0)node --version
): v15.11.0npm --version
): 7.0.14The text was updated successfully, but these errors were encountered: