npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

web3-nodejs-provider

v0.1.3

Published

HD Wallet-enabled Web3 provider

Downloads

8

Readme

web3-provider-nodejs

HD Wallet-enabled Web3 provider. Use it to sign transactions for addresses derived from a 12 or 24 word mnemonic.

Note: This is fork of https://www.npmjs.com/package/@truffle/hdwallet-provider with changes:

  • Explicitly provider private keys, mnemomic (or both)
  • Removed sharedNonce option
  • provider.stop is handled by environment, needless to call provider.stop()

Install

$ npm install web3-nodejs-provider
$ yarn add web3-nodejs-provider

Requirements

Node >= 12 
Web3 ^1.2.0

General Usage

You can use this provider wherever a Web3 provider is needed. Suitable for use in Nodejs, Deno runtimes where window.ethereum is not available.

Instantiation

You can instantiate Web3NodejsProvider 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 | [ ] | Specify to enable signed transactions that are EIP-155 compliant for major chains. |

Some examples can be found below:

const Web3NodejsProvider = require("web3-nodejs-provider");
const Web3 = require("web3");
const mnemonicPhrase = "mountains supernatural bird..."; // 12 word mnemonic

let provider = new Web3NodejsProvider({
  mnemonic: {
    phrase: mnemonicPhrase
  },
  providerOrUrl: "http://localhost:8545"
});

// Or, alternatively pass in a zero-based address index.
provider = new Web3NodejsProvider({
  mnemonic: mnemonicPhrase,
  providerOrUrl: "http://localhost:8545",
  addressIndex: 5
});

// Or, use your own hierarchical derivation path
provider = new Web3NodejsProvider({
  mnemonic: mnemonicPhrase,
  providerOrUrl: "http://localhost:8545",
  numberOfAddresses: 1,
  shareNonce: true,
  derivationPath: "m/44'/137'/0'/0/"
});

// To make HDWallet less "chatty" over JSON-RPC,
// configure a higher value for the polling interval.
provider = new Web3NodejsProvider({
  mnemonic: {
    phrase: mnemonicPhrase
  },
  providerOrUrl: "http://localhost:8545",
  pollingInterval: 8000
});

// HDWalletProvider is compatible with Web3. Use it at Web3 constructor, just like any other Web3 Provider
const web3 = new Web3(provider);

// Or, if web3 is alreay initialized, you can call the 'setProvider' on web3, web3.eth, web3.shh and/or web3.bzz
web3.setProvider(provider)

// ...
// Write your code here.
// ...

// At termination, `provider.engine.stop()' should be called to finish the process elegantly.
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 | [ ] | Specify to enable signed transactions that are EIP-155 compliant for major chains. |

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 Web3NodejsProvider = require("web3-nodejs-provider");
//load single private key as string
let provider = new Web3NodejsProvider("3f841bf589fdf83a521e55d51afddc34fa65351161eead24f064855fc29c9580", "http://localhost:8545");

// Or, pass an array of private keys, and optionally use a certain subset of addresses
const privateKeys = [
  "3f841bf589fdf83a521e55d51afddc34fa65351161eead24f064855fc29c9580",
  "9549f39decea7b7504e15572b2c6a72766df0281cea22bd1a3bc87166b1ca290",
];

provider = new Web3NodejsProvider(privateKeys, "http://localhost:8545", 0, 2); //start at address_index 0 and load both addresses

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.

Similar work

Compose own providers (Made to work with MetaMask Browser Wallet only): https://github.com/MetaMask/web3-provider-engine

Support

If you wish to support this project, please do so on:

  1. BTC: 3AKZndQ3fgj48emakUXe81dyW7zTJQm7wv
  2. LTC: MQFsxZ42CD3HEyucM1jj2WM4xbYibYWsVg
  3. ETH: 0xB61ED210326FEb11A1f7048c77c404553fCed702