-
|
Lesson 4 says (unless I misunderstood) that we should use the "Network ID" reported by Ganache as chain ID for the transaction. In my case, Ganache reports a Network ID of 5777 (see screen capture below), but if I use that, web3.py complains when I run deploy.py with the following message:
When I set my chain ID to 1337, everything goes fine and deploy.py executes properly. Any idea why I have this behavior ? Searched the documentation and the web in general to no avail... Thanks.
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment · 4 replies
-
|
I ran into the same problem, what I did was to go into the settings of ganache->server->network ID in which I changed my network ID to 1337. This will change your address and private key so make sure to update those as well in your code. |
Beta Was this translation helpful? Give feedback.
-
|
Glad to see it's not just me 😁. Seems like a problem with Ganache. Anyway, it was not really blocking. Thanks for your reply. |
Beta Was this translation helpful? Give feedback.
-
|
Awesome work hear all! Great Q&A |
Beta Was this translation helpful? Give feedback.
-
|
I had the same issue, thanks for the update. |
Beta Was this translation helpful? Give feedback.
-
|
I also ran into the same issue, but I fixed it by only changing the chain_id to 1337 as the machine wished and not change the server settings, will that cause any other problem? |
Beta Was this translation helpful? Give feedback.
I ran into the same problem, what I did was to go into the settings of ganache->server->network ID in which I changed my network ID to 1337. This will change your address and private key so make sure to update those as well in your code.