-
Notifications
You must be signed in to change notification settings - Fork 201
openzeppelin-cli uses the wrong account #1579
Comments
So. I modified rinkeby_local: {
provider: () => new HDWalletProvider(
mnemonic, `http://172.27.96.1:8545`, 2 // <-- added 1 more argument
),
networkId: 4,
gasPrice: 10e9
} I did this so that HDWalletProvider starts generating accounts from 2 (zero indexed). I then selected account 0 and deployed. |
Hi @nicexe! I’m sorry that you had this issue. We have been able to reproduce this issue by following these steps:
But the contract is actually deployed from the default account. See: https://rinkeby.etherscan.io/address/0x3FaFDb81B9DAC664B4e1F2b276865AC6bC94eC65
Thanks so much for reporting it! The project owner will review and triage this issue as soon as they can. In the meantime, you can try the following workaround: Instead of
The contract is deployed using the specified account: https://rinkeby.etherscan.io/address/0x0d0FE29b73793370cF54c4Cb549d683c985C2B48 |
I noticed an odd behavior while using openzeppelin-cli where it uses the account in the list that @truffle/hdwallet-provider provides no matter what account was actually selected.
I'm using
@openzeppelin/cli
version2.8.2
and@truffle/hdwallet-provider
version1.0.42
Here is my
networks.js
:Here is how I deploy a contract
This is what the node says:
And this is what etherscan says:
I don't really know if the issue is with openzeppelin-cli or with @truffle/hdwallet-provider
The text was updated successfully, but these errors were encountered: