Basic Usage - Wiki OpenEthereum Documentation

Once the syncing is complete, new transactions can be sent. Before relaying a transaction Secure Transaction Signer has to be used to sign it.


Use openethereum --help to find out about available options. To avoid adding options on every run of OpenEthereum a config file.


You can connect to the Görli testnet with openethereum --chain goerli.

You can override the normal boot nodes with --bootnodes, i.e., you might run a local bootnode and sync from that by running:

$ openethereum --bootnodes enode://YOU_BOOT_NODE_ID_HERE@

To maintain permanent connection to your own set of nodes, you can wire them with the --reserved-peers feature. Simply place all node addresses you want to connect to (enode://..., one per line) into a text file, e.g., reserved.txt, and run OpenEthereum with:

$ openethereum --reserved-peers /path/to/reserved.txt


Assuming you start with JSONRPC API enabled (default), then Ethereum’s JSON-RPC can be used, e.g.:

$ curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_getBalance","params":["0x0037a6b811ffeb6e072da21179d11b1406371c63", "latest"],"id":1}'

JavaScript Console

Ethereum has the web3 Javascript API for interacting with an Ethereum client.

Node.js CLI Console

OpenEthereum doesn’t include a JavaScript interpreter but if you want to use an interactive JavaScript console, you can install node and npm and use its console. Once you have node/NPM installed, you’ll just need to install the latest Web3 module:

$ npm install web3

From then on you just need to run node and require the Web3 module:

$ node
> Web3 = require("web3")
> web3 = new Web3(new Web3.providers.HttpProvider("http://localhost:8545"));

After this point, you’ll be able to use the Web3 API from with this environment, e.g.:

> web3.eth.blockNumber