Basic Usage - Wiki Parity Tech 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 parity --help to find out about available options. To avoid adding options on every run of Parity a config file. The file can be easily generated using this tool.


You can connect to the Ropsten testnet with parity --chain ropsten or to the Kovan testnet with parity --chain kovan.

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

$ parity --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 Parity with:

$ parity --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

Parity 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
Legacy Geth Console

As of this writing, Parity’s IPC socket can be readily attached to by Geth. To do this, run Parity with IPC enabled (IPC is by default on, unless the --no-ipc option is passed). You can then run Geth with the attach command and pass the IPC file, which is specified by the --ipc-path flag to parity, just like so:


$ geth attach ~/.local/share/io.parity.ethereum/jsonrpc.ipc


$ geth attach ~/Library/Application\ Support/io.parity.ethereum/jsonrpc.ipc

It’s no longer required to run Parity in --geth compatibility mode to use the Geth console.