"truffle migrate —reset" failed from "geth 1.10.0" #3913
Comments
|
+1 I thought I was going crazy @daenamkim! Everything was working until randomly started getting this error, I just started seeing this error about 3-4 hours ago. Did you by any chance change your secrets you were using? That was the last thing I remember doing before seeing this, but I am unaware if it was related. I am also on a mac btw npx truffle migrate --reset --network ropsten
Compiling your contracts...
===========================
> Everything is up to date, there is nothing to compile.
Starting migrations...
======================
> Network name: 'ropsten'
> Network id: 3
> Block gas limit: 8000000 (0x7a1200)
1_initial_migration.js
======================
Replacing 'Migrations'
----------------------
Error: *** Deployment Failed ***
"Migrations" -- only replay-protected (EIP-155) transactions allowed over RPC.
Results of "networks --clean"npx truffle networks --clean
TypeError: Cannot convert undefined or null to objectI also noticed how little information there is about this specific issue. The only documentation I noticed was what OP mentioned above with --rpc.allow-unprotected-txsEDIT: |
|
@daenamkim what network are you targeting? |
|
Also looking at that gitter link @daenamkim , seems like multiple people are having this issue.. it can't be local then... It could be a number of things now that I'm seeing this... for it to randomly occur when I made no updates on my machine, that is telling. hm |
|
Temporarily, how can we make use of This seems insecure though, and this doesn't seem like a production-ready workaround... Lastly, this seems concerning that an issue like this can effect so many developers at once... @daenamkim you said you updated while running a The only thing I did was switch secrets to another account, and then switched back. Perhaps this could've forced an upgrade?.. this is strange though BTW just running My final thought is perhaps several network nodes upgrade to pangea expanse today... |
|
I am having the same issue. I want to (re)deploy my contracts to Ropsten and I am using Infura. I believe I want to somehow pass |
|
Yea, I don't think so either @Siegrift , since the nodes themselves are running the runtime itself, those nodes would have to run that command. I am sure being able to pass command line args like I wonder if this means we only need to submit replay-protected TXs moving forward... |
|
More context for other readers, in addition to the links above: |
|
@Jovonni |
|
Definitely seems to be caused by Infura upgrading to geth v1.10.1 but I don't blame them for that, nor do I think the solution is to add the --rpc.allow-unprotected-txs on their side. It would be nice to be able to pass an argument to Infura that adds the flag when really required, but the real solution would be to have truffle add the chain ID to transactions as per EIP 155. Thanks to @daenamkim for starting this thread. Sounds like many of us have spent some hours scratching our heads already and for sure many others will until it's fixed. |
|
Agreed @jpataylor I have been looking at truffle's core in attempts to add the chainID to transactions myself, and submit it as a PR. Still looking... |
|
For anyone who also waiting for the fix - Alchemy updated their nodes to be running with |
|
Infura has re-enabled support for non-eip-155 transactions to help users on Ropsten until Truffle has a fix ready. Full details here: https://community.infura.io/t/berlin-fork-and-strict-checking-for-eip-155-transaction-compatibility/2609 |
|
Does anyone have any documentation on how to sign the transactions to adhere to EIP 155? looking for definitive documentation. Want to ensure to be ahead of the curve on this |
|
Hi, is there some progress on the proper fix for this on truffle side? I hope this will get fixed until infura disables the |
|
@haltman-at this was NOT fixed by #3923. See also #3935. |
|
Question, are these problems still happening on Truffle 5.2.6? Thank you! |
|
Using Truffle version 5.2.6 and Geth 1.10.1-stable I am able to migrate a project successfully (with @truffle/hdwallet-provider). Can anyone else confirm the same results or still get errors? |
|
@eggplantzzz Truffle version 5.2.6 did NOT resolve this for me. |
|
OK, this should be resolved in 5.3.0, so I'm going to close this. Let us know if it's not and we can reopen. |
|
I'm still getting the same problem. Truffle v5.3.6 and @truffle/[email protected] @1.2.6 @1.3.0 |
|
Could you try updating |
|
Ahh this is infuriating. Trying to deploy to matic testnet as per https://docs.matic.network/docs/develop/truffle these instructions, and it hates me. |
FYI Updating @truffle/hdwallet-provider to 1.4.0 worked for me :) |
worked for me too. Also found out I somehow had "hdwallet-provider" instead of "@truffle/hdwallet-provider" as my dependency, which was deprecated so its version number wouldn't go any higher. Confused me briefly. If anyone else is stuck here make sure you check that you have the right dependency name. |
|
OK, I'm going to leave this closed for now then. @apolosan, let us know if there's still a problem after upgrading to 1.4.0. |
|
@haltman-at I am able to trigger transaction, but the transaction seems to be pending forever on mumbai |
|
@Xuefeng-Zhu That sounds like an unrelated problem. Could you perhaps file a new issue for that? Thanks! |
|
There seems to be a recession. I originally used Truffle 5.1.50 when I came across this problem. After reading up on this thread, I installed Truffle 5.3.10 and continued to have the problem: However, the problem does not occur with Truffle 5.3.0. |
|
@m1cm1c Just to be certain, are you using a version of |
|
@hatman-at I'm not using |
|
@eggplantzzz @haltman-at @m1cm1c
|
See issue truffle-box#1 and related issues linked below. Fixes below error when attempting to migrate the default contract. ``` Error: while migrating SimpleStorage: only replay-protected (EIP-155) transactions allowed over RPC ``` trufflesuite/truffle#3913 trufflesuite/truffle#4147
|
I keep having this error with: I also tried with truffle: Also I tried different RPC, like: And the same error happens: "Migrations" -- only replay-protected (EIP-155) transactions allowed over RPC. And I am having this in other networks as well, like Fantom, not only Polygon... more info: truffle.js: command: error: package.json: truffle version any ideas? |
|
I noticed this bug is closed, should I open a new one? |
|
@WPSmartContracts Yes, I would suggest opening a new issue. |
|
Do not forget to update - var HDWalletProvider = require("@truffle/hdwallet-provider"); This will ensure you are pointing to the corrector hdwallet version. It works! |
|
@WPSmartContracts did you file a new issue? @haltman-at I'm seeing this issue when running truffle test with ganachev7, but not with ganache v6. It's flakey though - sometimes the tests will run, other time it will fail at this deployment step. |
|
@samskiter I would suggest filing a new issue for this, as this one's got a lot to sort through. |
|
hey i had the same issue
But could solve this with this help in my truffle-confic |
Issue
I have been working with truffle and experienced
truffle migrate —resetis not working from geth 1.10.0, it showedonly replay-protected (EIP-155) transactions allowed over RPC. I found out workaround from https://github.com/ethereum/go-ethereum/releases/tag/v1.10.0, adding--rpc.allow-unprotected-txson local geth running. For local geth will be fine but I am not sure after all remote nodes (of using geth) are updated to v1.10.x.Steps to Reproduce
truffle migrate --resetmultiple times (I am not sure on the first because I have updated geth while I was working)Expected Behavior
truffle migrate --resetshould work without any problem (in my opinion) or show a guide what a has to do at least.Actual Results
Environment
truffle version): Truffle v5.2.3 (core: 5.2.3)node --version): v14.15.5npm --version): 6.14.11 (FYI, I am not using npm but yarn 1.22.10)The text was updated successfully, but these errors were encountered: