Skip to content

Latest commit

 

History

History
60 lines (46 loc) · 2.36 KB

README.md

File metadata and controls

60 lines (46 loc) · 2.36 KB

Warning: this tool is experimental. It should work for GNU/Linux and hopefully on Mac OS.

ethnode, run an Ethereum node for test and development

ethnode is a zero configuration tool to run a local Ethereum node. It supports both Parity and Geth.

Try it out:

npm install -g ethnode
ethnode

ethnode automatically:

  • downloads the latest stable version of geth or parity
  • configures geth or parity to run in a single node network using the clique (Geth) or InstantSeal (Parity) consensus engine (transactions are processed instantly)
  • provides 10 unlocked accounts with 100ETH each
  • enables all RPC endpoints (personal, db, eth, net, web3, debug and more)
  • allows CORS from any domain (so you can use it with remix)

By default ethnode runs geth. If you want to run parity type ethnode parity.

Examples

Start ethnode and store the data in a specific directory

Every time you run ethnode, it creates a new temporary directory to store the data. If you want to persist the data across

ethnode --workdir=mydata

Start ethnode and allocate 100ETH to one or more target addresses

Sometimes you want to allocate Ether to some specific addresses (maybe some other accounts you have on MetaMask). This is an alternative approach to import a private key to your MetaMask extension.

ethnode --allocate=0xad7b5e515e557b2dc4d0625d206394b502412003,0xecdd5b467e38731bfad4bd75faa45c7d58e41b49

Start

FAQ

Why not just running parity --config dev?

Parity has a nice feature to run it as a private development chain (aka test RPC).

While testing it, I run into some problems, like:

  • address management
  • outdated genesis file
  • the default configuration (--config dev) doesn't:
    • open up CORS
    • unlock the test keys

Why not just running geth --dev?

More or less for the same reasons mentioned above.

Why not ganache-cli?

Ganache sometimes is not enough.