@truffle/hdwallet-provider
HD Wallet-enabled Web3 provider. Use it to sign transactions for addresses derived from a 12 or 24 word mnemonic.
Install
$ npm install @truffle/hdwallet-provider
Requirements
Node >= 7.6
Web3 ^1.2.0
General Usage
You can use this provider wherever a Web3 provider is needed, not just in Truffle. For Truffle-specific usage, see next section.
By default, the HDWalletProvider
will use the address of the first address that's generated from the mnemonic. If you pass in a specific index, it'll use that address instead.
Instantiation
You can instantiate hdwallet-provider
with options passed in an object with
named keys. You can specify the following options in your object:
Parameters:
Parameter | Type | Default | Required | Description |
---|
mnemonic | object|string | null | [ ] | Object containing phrase and password (optional) properties. phrase is a 12 word mnemonic string which addresses are created from. Alternately the value for mnemonic can be a string with your mnemonic phrase. |
privateKeys | string[] | null | [ ] | Array containing 1 or more private keys. |
providerOrUrl | string|object | null | [x] | URI or Ethereum client to send all other non-transaction-related Web3 requests |
addressIndex | number | 0 | [ ] | If specified, will tell the provider to manage the address at the index specified |
numberOfAddresses | number | 1 | [ ] | If specified, will create numberOfAddresses addresses when instantiated |
shareNonce | boolean | true | [ ] | If false , a new WalletProvider will track its own nonce-state |
derivationPath | string | "m/44'/60'/0'/0/" | [ ] | If specified, will tell the wallet engine what derivation path should use to derive addresses. |
pollingInterval | number | 4000 | [ ] | If specified, will tell the wallet engine to use a custom interval when polling to track blocks. Specified in milliseconds. |
chainId | `number/ | string` | undefined | [ ] |
Some examples can be found below:
const HDWalletProvider = require("@truffle/hdwallet-provider");
const Web3 = require("web3");
const mnemonicPhrase = "mountains supernatural bird...";
let provider = new HDWalletProvider({
mnemonic: {
phrase: mnemonicPhrase
},
providerOrUrl: "http://localhost:8545"
});
provider = new HDWalletProvider({
mnemonic: mnemonicPhrase,
providerOrUrl: "http://localhost:8545",
addressIndex: 5
});
provider = new HDWalletProvider({
mnemonic: mnemonicPhrase,
providerOrUrl: "http://localhost:8545",
numberOfAddresses: 1,
shareNonce: true,
derivationPath: "m/44'/137'/0'/0/"
});
provider = new HDWalletProvider({
mnemonic: {
phrase: mnemonicPhrase
},
providerOrUrl: "http://localhost:8545",
pollingInterval: 8000
});
const web3 = new Web3(provider);
web3.setProvider(provider)
provider.engine.stop();
Note: If both mnemonic and private keys are provided, the mnemonic is used.
Using the legacy interface (deprecated)
The legacy interface is deprecated and it is recommended to pass options in an
object as detailed above. The following method of passing options is here
primarily to document the interface thoroughly and avoid confusion.
You can specify the following options in the order below.
Pass undefined
if you want to omit a parameter.
Parameters:
Parameter | Type | Default | Required | Description |
---|
mnemonic /privateKeys | string /string[] | null | [x] | 12 word mnemonic which addresses are created from or array of private keys. |
providerOrUrl | string|object | null | [x] | URI or Ethereum client to send all other non-transaction-related Web3 requests |
addressIndex | number | 0 | [ ] | If specified, will tell the provider to manage the address at the index specified |
numberOfAddresses | number | 1 | [ ] | If specified, will create numberOfAddresses addresses when instantiated |
shareNonce | boolean | true | [ ] | If false , a new WalletProvider will track its own nonce-state |
derivationPath | string | "m/44'/60'/0'/0/" | [ ] | If specified, will tell the wallet engine what derivation path should use to derive addresses. |
chainId | `number/ | string` | undefined | [ ] |
Instead of a mnemonic, you can alternatively provide a private key or array of
private keys as the first parameter. When providing an array, addressIndex
and numberOfAddresses
are fully supported.
const HDWalletProvider = require("@truffle/hdwallet-provider");
let provider = new HDWalletProvider("3f841bf589fdf83a521e55d51afddc34fa65351161eead24f064855fc29c9580", "http://localhost:8545");
const privateKeys = [
"3f841bf589fdf83a521e55d51afddc34fa65351161eead24f064855fc29c9580",
"9549f39decea7b7504e15572b2c6a72766df0281cea22bd1a3bc87166b1ca290",
];
provider = new HDWalletProvider(privateKeys, "http://localhost:8545", 0, 2);
NOTE: This is just an example. NEVER hard code production/mainnet private
keys in your code or commit them to git. They should always be loaded from
environment variables or a secure secret management system.
Truffle Usage
You can easily use this within a Truffle configuration. For instance:
truffle-config.js
const HDWalletProvider = require("@truffle/hdwallet-provider");
const mnemonicPhrase = "mountains supernatural bird ...";
module.exports = {
networks: {
development: {
host: "localhost",
port: 8545,
network_id: "*"
},
ropsten: {
provider: () =>
new HDWalletProvider({
mnemonic: {
phrase: mnemonicPhrase
},
providerOrUrl: "https://ropsten.infura.io/v3/YOUR-PROJECT-ID",
numberOfAddresses: 1,
shareNonce: true,
derivationPath: "m/44'/1'/0'/0/"
}),
network_id: '3',
}
}
};